Re: RFR: JDK-8281082: Improve javadoc references to JOSS [v2]

2022-02-01 Thread Alan Bateman
On Tue, 1 Feb 2022 22:33:46 GMT, Joe Darcy wrote: >> The references to JOSS, the Java Object Serialization Specification, are not >> done consistently in the API javadoc. This should be improved. >> >> I'll update copyright years before pushing. > > Joe Darcy has updated the pull request increm

Integrated: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Joe Darcy
On Tue, 1 Feb 2022 21:11:39 GMT, Joe Darcy wrote: > The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. This pull request has now been integrated. Changese

Re: RFR: JDK-8281082: Improve javadoc references to JOSS [v2]

2022-02-01 Thread Joe Darcy
> The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. Joe Darcy has updated the pull request incrementally with one additional commit since the last revision

Re: RFR: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Lance Andersen
On Tue, 1 Feb 2022 21:11:39 GMT, Joe Darcy wrote: > The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. Marked as reviewed by lancea (Reviewer). --

RFR: 8280890: Cannot use '-Djava.system.class.loader' with class loader in signed JAR

2022-02-01 Thread Sean Mullan
This fixes a bootstrapping issue if a custom system class loader is set with the `-Djava.system.class.loader` option and the custom class loader is inside a signed JAR. In order to load the custom class loader, the runtime must verify the signed JAR first, and the algorithm constraint code trie

Re: RFR: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Naoto Sato
On Tue, 1 Feb 2022 21:11:39 GMT, Joe Darcy wrote: > The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. Marked as reviewed by naoto (Reviewer). ---

Re: RFR: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Roger Riggs
On Tue, 1 Feb 2022 21:11:39 GMT, Joe Darcy wrote: > The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. Marked as reviewed by rriggs (Reviewer). --

Re: RFR: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Iris Clark
On Tue, 1 Feb 2022 21:11:39 GMT, Joe Darcy wrote: > The references to JOSS, the Java Object Serialization Specification, are not > done consistently in the API javadoc. This should be improved. > > I'll update copyright years before pushing. Marked as reviewed by iris (Reviewer).

RFR: JDK-8281082: Improve javadoc references to JOSS

2022-02-01 Thread Joe Darcy
The references to JOSS, the Java Object Serialization Specification, are not done consistently in the API javadoc. This should be improved. I'll update copyright years before pushing. - Commit messages: - JDK-8281082: Improve javadoc references to JOSS Changes: https://git.openjdk

Integrated: 8275914: SHA3: changing java implementation to help C2 create high-performance code

2022-02-01 Thread Boris Ulasevich
On Wed, 15 Dec 2021 09:20:38 GMT, Boris Ulasevich wrote: > Background > > The goal is to improve SHA3 implementation performance as it runs up to two > times slower than native (OpenSSL, measured on AMD64 and AArch6464) > implementation. Some hardware provides SHA3 accelerators, but most (AMD

Re: RFR: 8275914: SHA3: changing java implementation to help C2 create high-performance code [v3]

2022-02-01 Thread Paul Hohensee
On Tue, 1 Feb 2022 09:52:46 GMT, Boris Ulasevich wrote: >> Background >> >> The goal is to improve SHA3 implementation performance as it runs up to two >> times slower than native (OpenSSL, measured on AMD64 and AArch6464) >> implementation. Some hardware provides SHA3 accelerators, but most (

Re: RFR: 8275914: SHA3: changing java implementation to help C2 create high-performance code [v3]

2022-02-01 Thread Anthony Scarpino
On Tue, 1 Feb 2022 09:52:46 GMT, Boris Ulasevich wrote: >> Background >> >> The goal is to improve SHA3 implementation performance as it runs up to two >> times slower than native (OpenSSL, measured on AMD64 and AArch6464) >> implementation. Some hardware provides SHA3 accelerators, but most (

Re: RFR: 8275914: SHA3: changing java implementation to help C2 create high-performance code [v3]

2022-02-01 Thread Boris Ulasevich
> Background > > The goal is to improve SHA3 implementation performance as it runs up to two > times slower than native (OpenSSL, measured on AMD64 and AArch6464) > implementation. Some hardware provides SHA3 accelerators, but most (AMD64 and > most AArch64) do not. > > For AArch64 hardware th

Re: RFR: 8275914: SHA3: changing java implementation to help C2 create high-performance code [v2]

2022-02-01 Thread Boris Ulasevich
> Background > > The goal is to improve SHA3 implementation performance as it runs up to two > times slower than native (OpenSSL, measured on AMD64 and AArch6464) > implementation. Some hardware provides SHA3 accelerators, but most (AMD64 and > most AArch64) do not. > > For AArch64 hardware th