RFR: 8312425: [vectorapi] AArch64: Optimize vector math operations with SLEEF [v11]
Andrew Haley
aph at openjdk.org
Tue Jul 16 10:44:57 UTC 2024
On Tue, 16 Jul 2024 09:48:55 GMT, Andrew Haley <aph at openjdk.org> wrote:
> @theRealAph Thanks for clarification.
>
> I think there are several different parts involved in the above discussion, please kindly correct me if I misunderstood.
>
> 1. package builders. This is about the release of jdk (both src and binary), by either openjdk, adoptium, or any other downstream vendors.
>
> 2. jdk daily development. This is about to modify, build, run/test jdk daily by jdk developers.
>
> For the package builders, original sleef source is
may be
> necessary; for the jdk daily development, only pre-generated sleef inline headers are necessary.
Yes, most of the time. Some devs will want to be more thorough.
> The script to pre-generate sleef inline headers is only triggerred by package builders (and I think it involves some scripts which are not part of jdk source ? e.g. the script to trigger pre-generating script),
No: all of the scripts to generate the preprocessed source from the SLEEF source must in the OpenJDK source.
> but for jdk daily development, we just need pre-generated sleef inline headers. Am I understanding correctly above?
Yes, most of the time.
Bear in mind that convenient daily development of OpenJDK is important, because we don't want to discourage developers. But we've never treated the size of the repo as one of our primary considerations.
> I have not particular preference which options to take. My only concern is how long it will take to make that decision. If it could take rather long time, can we take several incremental steps to achieve the final goal? e.g.
We're only a couple of weeks away from the summit. What would be a long time?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/18605#issuecomment-2230581736
More information about the build-dev
mailing list