On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
I'm not sure what you mean by hotspot requiring a special review, but
serviceability code does
On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
globalDefinitions_visCPP.hpp (and the corresponding globalDefinitions file for
gcc based compilers)
On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
> I don't think I can touch the freetype code since I think it's an external
> library that was
On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
Just checked, the pragmas in the freetype code now seems to be pointless since
there is no alignment
On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
I don't think I can touch the freetype code since I think it's an external
library that was
On Fri, 31 Mar 2023 06:07:39 GMT, Julian Waters wrote:
> C11 has been stable for a long time on all platforms, so native code can use
> the standard alignas operator for alignment requirements
I don't have any comments on this change in general (it's not something I've
dealt with in the
C11 has been stable for a long time on all platforms, so native code can use
the standard alignas operator for alignment requirements
-
Commit messages:
-
- GSSLibStub.c
- ArrayReferenceImpl.c
- Alignment outside of HotSpot should be enforced by alignas instead of
compiler
