Re: RFR: 8354273: Restore even more pointless unicode characters to ASCII [v2]

2025-04-15 Thread Phil Race
On Thu, 10 Apr 2025 10:36:31 GMT, Magnus Ihse Bursie wrote: >> As a follow-up to >> [JDK-8354213](https://bugs.openjdk.org/browse/JDK-8354213), I found some >> additional places where unicode characters are unnecessarily used instead of >> pure ASCII. > > Magnus Ihse Bursie has updated the pul

Re: RFR: 8349503: Consolidate multi-byte access into ByteArray

2025-02-13 Thread Phil Race
On Thu, 6 Feb 2025 14:30:30 GMT, Per Minborg wrote: >> `MethodHandles.byteArrayViewVarHandle` exposes checked multi-byte access to >> byte arrays via VarHandle. This larger access speeds up many operations, yet >> it cannot be used in early bootstrap, and as a result, people tend to use >> `Un

Re: RFR: 8347123: Add missing @serial tags to other modules [v2]

2025-01-28 Thread Phil Race
On Fri, 24 Jan 2025 10:58:24 GMT, Hannes Wallnöfer wrote: >> Please review a doc-only change to mostly add missing `@serial` javadoc >> tags. This is a sub-task of [JDK-8286931] to allow us to re-enable the >> javadoc `-serialwarn` option in the JDK doc build, which has been disabled >> since

Re: RFR: 8347123: Add missing @serial tags to other modules

2025-01-22 Thread Phil Race
On Wed, 22 Jan 2025 09:23:10 GMT, Hannes Wallnöfer wrote: >> src/java.datatransfer/share/classes/java/awt/datatransfer/DataFlavor.java >> line 1288: >> >>> 1286: >>> 1287: /** >>> 1288: * Serializes this {@code DataFlavor}. >> >> This most definitely changes the serialisation spec. S

Re: RFR: 8347123: Add missing @serial tags to other modules

2025-01-21 Thread Phil Race
On Wed, 8 Jan 2025 20:13:50 GMT, Hannes Wallnöfer wrote: > Please review a doc-only change to mostly add missing `@serial` javadoc tags. > This is a sub-task of [JDK-8286931] to allow us to re-enable the javadoc > `-serialwarn` option in the JDK doc build, which has been disabled since JDK > 1

Re: RFR: 8346773: Fix unmatched brackets in source files

2024-12-23 Thread Phil Race
On Mon, 23 Dec 2024 20:29:09 GMT, Phil Race wrote: >> test/jdk/sanity/client/lib/SwingSet3/src/com/sun/swingset3/demos/table/resources/oscars.xml >> line 2: >> >>> 1: >>> 2: http://www.fatdog.com/oscar-results"; >> >> Does this change aff

Re: RFR: 8346773: Fix unmatched brackets in source files

2024-12-23 Thread Phil Race
On Mon, 23 Dec 2024 19:30:56 GMT, Kim Barrett wrote: >> This patch fixes unmatched brackets in some source files. > > test/jdk/sanity/client/lib/SwingSet3/src/com/sun/swingset3/demos/table/resources/oscars.xml > line 2: > >> 1: >> 2: http://www.fatdog.com/oscar-results"; > > Does this change

Re: RFR: 8346773: Fix unmatched brackets in source files

2024-12-23 Thread Phil Race
On Mon, 23 Dec 2024 19:42:34 GMT, Kim Barrett wrote: > > That makes it harder to review and to manage the review, because it is > > large and affects a wide range of areas, so may need many reviewers. > > And many of the appropriate reviewers might be unavailable for a while, since > it's righ

Re: RFR: 8346377: Properly support static builds for Windows

2024-12-19 Thread Phil Race
On Tue, 17 Dec 2024 15:41:51 GMT, Magnus Ihse Bursie wrote: > When the static launcher was introduced in > [JDK-8339480](https://bugs.openjdk.org/browse/JDK-8339480), due to time and > resource constraints, it was only working properly on Linux and macOS, while > the Windows port compiled but

Re: RFR: 8346377: Properly support static builds for Windows

2024-12-19 Thread Phil Race
On Tue, 17 Dec 2024 15:41:51 GMT, Magnus Ihse Bursie wrote: > When the static launcher was introduced in > [JDK-8339480](https://bugs.openjdk.org/browse/JDK-8339480), due to time and > resource constraints, it was only working properly on Linux and macOS, while > the Windows port compiled but

Re: RFR: 8346570: SM cleanup of tests for Beans and Serialization

2024-12-18 Thread Phil Race
On Wed, 18 Dec 2024 14:58:26 GMT, Roger Riggs wrote: > Continuing SM removal cleanup of tests for test/jdk/java/beans and > test/jdk/java/io/Serializable. > Removing doPrivileged, Permissions, and SecurityException. Beans changes look fine - Marked as reviewed by prr (Reviewer).

Re: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3]

2024-12-10 Thread Phil Race
On Tue, 10 Dec 2024 09:31:21 GMT, Prasanta Sadhukhan wrote: > not sure why client label is added, no java.desktop/accessibility files are > in there I was puzzling over that too. - PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2532895836

Integrated: 8344799: Remove permissions checks from java.awt.Desktop

2024-11-21 Thread Phil Race
On Thu, 21 Nov 2024 22:21:47 GMT, Phil Race wrote: > Clean up permission checks in java.awt.Desktop class > Also remove no longer needed exports from java.base to java.desktop This pull request has now been integrated. Changeset: 50c099d6 Author: Phil Race URL:

Re: RFR: 8344799: Remove permissions checks from java.awt.Desktop [v2]

2024-11-21 Thread Phil Race
> Clean up permission checks in java.awt.Desktop class > Also remove no longer needed exports from java.base to java.desktop Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8344799 - Changes: - all:

Re: RFR: 8344799: Remove permissions checks from java.awt.Desktop

2024-11-21 Thread Phil Race
On Thu, 21 Nov 2024 23:46:14 GMT, Alexander Zvegintsev wrote: > There is a mention of the `GetPropertyAction` left in the comment: > > https://github.com/openjdk/jdk/blob/c199f5326b8dd41f33a12e5db7552331e0844601/src/java.desktop/share/classes/sun/awt/util/PerformanceLogger.java#L130 Did you me

RFR: 8344799: Remove permissions checks from java.awt.Desktop

2024-11-21 Thread Phil Race
Clean up permission checks in java.awt.Desktop class Also remove no longer needed exports from java.base to java.desktop - Commit messages: - 8344799 Changes: https://git.openjdk.org/jdk/pull/22311/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22311&range=00 Issue: http

Re: RFR: 8342869: Errors related to unused code on Windows after 8339120 in awt

2024-11-19 Thread Phil Race
On Wed, 23 Oct 2024 05:07:37 GMT, Julian Waters wrote: > After 8339120, gcc began catching many different instances of unused code in > the Windows specific codebase. Some of these seem to be bugs. I've taken the > effort to mark out all the relevant globals and locals that trigger the > unuse

Integrated: 8344065: Remove SecurityManager uses from the java.datatransfer module

2024-11-14 Thread Phil Race
On Thu, 14 Nov 2024 23:51:24 GMT, Phil Race wrote: > remove uses of SM APIs from the java.datatransfer module. Also cleans up the > now un-needed export from java.base This pull request has now been integrated. Changeset: 99070658 Author: Phil Race URL: https://git.openjdk.o

RFR: 8344065: Remove SecurityManager uses from the java.datatransfer module

2024-11-14 Thread Phil Race
remove uses of SM APIs from the java.datatransfer module. Also cleans up the now un-needed export from java.base - Commit messages: - 8344065 Changes: https://git.openjdk.org/jdk/pull/22127/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22127&range=00 Issue: https://bug

Re: RFR: 8343490: Update copyright year for JDK-8341692

2024-11-13 Thread Phil Race
On Tue, 5 Nov 2024 01:41:00 GMT, SendaoYan wrote: > Hi all, > The copyright year of some files which has been changed by > [JDK-8341692](https://bugs.openjdk.org/browse/JDK-8341692) wasn't update > correctly. This PR update the copyright year of > [JDK-8341692](https://bugs.openjdk.org/browse

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-11-08 Thread Phil Race
On Fri, 1 Nov 2024 18:06:47 GMT, Alexey Ivanov wrote: > > I'd not looked at this test before but when I do the thing I noticed is > > that createPrivateValue is no longer used. But I don't see a problem with > > keeping the rest of the test. > > @prrace Do I understand correctly that _“`create

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v9]

2024-11-08 Thread Phil Race
On Fri, 8 Nov 2024 13:49:55 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main cha

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v17]

2024-11-01 Thread Phil Race
On Fri, 1 Nov 2024 16:04:55 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v4]

2024-10-28 Thread Phil Race
On Mon, 28 Oct 2024 12:29:07 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-25 Thread Phil Race
On Fri, 25 Oct 2024 21:06:28 GMT, Harshitha Onkar wrote: >> test/jdk/javax/imageio/spi/AppletContextTest/IIOPluginTest.java line 42: >> >>> 40: } catch (ServiceConfigurationError sce) { >>> 41: System.out.println("Expected ServiceConfigurationError \n" >>> + sce); >>> 42:

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-25 Thread Phil Race
On Fri, 25 Oct 2024 21:23:26 GMT, Harshitha Onkar wrote: >> The tests with “Audit Core Reflection” in their summary fall into this >> category, we may consider removing them. > > @prrace Can you please advice on “Audit Core Reflection” category of tests. > I'm not 100% sure if these tests need

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-23 Thread Phil Race
On Wed, 23 Oct 2024 05:11:19 GMT, Prasanta Sadhukhan wrote: >> Sean Mullan has updated the pull request with a new target base due to a >> merge or a rebase. The pull request now contains 97 commits: >> >> - Merge remote-tracking branch 'jdk-sandbox/jep486' into JDK-8338411 >> - Change apiNo

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-23 Thread Phil Race
On Fri, 18 Oct 2024 19:03:30 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-22 Thread Phil Race
On Tue, 22 Oct 2024 15:22:08 GMT, Sean Mullan wrote: >> test/jdk/javax/swing/JComboBox/8080972/TestBasicComboBoxEditor.java line 26: >> >>> 24: import javax.swing.SwingUtilities; >>> 25: import javax.swing.plaf.basic.BasicComboBoxEditor; >>> 26: /* >> >> I think we have finally decided that jtr

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-21 Thread Phil Race
On Fri, 18 Oct 2024 19:03:30 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager

2024-10-15 Thread Phil Race
On Mon, 14 Oct 2024 13:52:24 GMT, Sean Mullan wrote: > This is the implementation of JEP 486: Permanently Disable the Security > Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The > [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the > main change

Re: RFR: 8341692: Implement JEP 490: ZGC: Remove the Non-Generational Mode [v2]

2024-10-09 Thread Phil Race
On Wed, 9 Oct 2024 12:57:36 GMT, Axel Boldt-Christmas wrote: >> This is the implementation task for `JEP 490: ZGC: Remove the >> Non-Generational Mode`. See the JEP for details. >> [JDK-8335850](https://bugs.openjdk.org/browse/JDK-8335850) > > Axel Boldt-Christmas has updated the pull request

Re: RFR: 8340326: Remove references to Applet in core-libs/security tests [v8]

2024-10-03 Thread Phil Race
On Thu, 3 Oct 2024 18:15:55 GMT, Justin Lu wrote: >> Please review this PR which removes usages of Applet within the corelibs >> tests. >> >> Most changes are removed comments/updated var names. The JBS issue lists >> more files than the ones included in this pull request, please see the >> c

Re: RFR: 8340326: Remove references to Applet in core-libs/security tests [v7]

2024-10-03 Thread Phil Race
On Fri, 27 Sep 2024 18:08:54 GMT, Justin Lu wrote: >> Please review this PR which removes usages of Applet within the corelibs >> tests. >> >> Most changes are removed comments/updated var names. The JBS issue lists >> more files than the ones included in this pull request, please see the >>

Re: RFR: 8340801: Disable ubsan checks in some awt/2d coding

2024-09-26 Thread Phil Race
On Wed, 25 Sep 2024 12:17:59 GMT, Matthias Baesken wrote: > There is some old awt/2d coding where warnings occur when running with ubsan > enabled binaries. > However at most of these locations the coding should work (at least on our > supported platform set) so the warnings can be disabled at

Re: RFR: 8340326: Remove references to Applet in core-libs/security tests [v4]

2024-09-26 Thread Phil Race
On Thu, 26 Sep 2024 16:25:21 GMT, Naoto Sato wrote: >> Justin Lu has updated the pull request incrementally with one additional >> commit since the last revision: >> >> review: update wording of instructions > > test/jdk/java/util/TimeZone/DefaultTimeZoneTest.java line 80: > >> 78:

Re: RFR: 8340326: Remove references to Applet in core-libs/security tests [v2]

2024-09-25 Thread Phil Race
On Wed, 25 Sep 2024 22:03:59 GMT, Justin Lu wrote: > Not sure if it will be ran by anyone as it is manual, I don't know about other vendors, but for Oracle, manual tests are run at least once on every release some time after RDP1 and before RDP2. - PR Comment: https://git.openjd

Re: RFR: 8339834: Replace usages of -mx and -ms in some tests [v3]

2024-09-11 Thread Phil Race
On Wed, 11 Sep 2024 09:19:21 GMT, Jaikiran Pai wrote: >> Can I please get a review of this trivial change which replaces the usages >> of `-mx` and `-ms` to `-Xmx` and `-Xms` in tests and in one code comment? >> >> As noted in https://bugs.openjdk.org/browse/JDK-8339834, these options are >> o

Re: RFR: 8338768: Introduce runtime lookup to check for static builds [v2]

2024-08-21 Thread Phil Race
On Wed, 21 Aug 2024 22:14:40 GMT, Magnus Ihse Bursie wrote: >> As a preparation for Hermetic Java, we need to have a way to look up during >> runtime if we are using a statically linked library or not. >> >> This change will be the first step needed towards compiling the object files >> only o

Re: RFR: 8336289: Obliterate most references to _snprintf in the Windows JDK [v3]

2024-08-01 Thread Phil Race
On Tue, 16 Jul 2024 08:59:20 GMT, Julian Waters wrote: >> snprintf has been available for all officially and unofficially supported >> compilers for Windows, Visual Studio since version 2015 and gcc since, well, >> forever. snprintf is conforming to C99 since the start when compiling using >>

Re: RFR: 8333827: JDK 23 RDP1 L10n resource files update [v3]

2024-06-12 Thread Phil Race
On Tue, 11 Jun 2024 19:28:27 GMT, Damon Nguyen wrote: >> This issue is responsible for updating the translations of all the >> localize(able) resources in the JDK. Primarily, the changes between JDK 22 >> RDP 1 and the integration of the JDK 23 RDP 1 L10n drop will be translated. >> >> The tra

Re: RFR: 8333827: JDK 23 RDP1 L10n resource files update

2024-06-10 Thread Phil Race
On Fri, 7 Jun 2024 22:46:44 GMT, Damon Nguyen wrote: > This issue is responsible for updating the translations of all the > localize(able) resources in the JDK. Primarily, the changes between JDK 22 > RDP 1 and the integration of the JDK 23 RDP 1 L10n drop will be translated. > > The translati

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v8]

2024-05-21 Thread Phil Race
On Fri, 17 May 2024 13:38:25 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v8]

2024-05-20 Thread Phil Race
On Fri, 17 May 2024 13:38:25 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v8]

2024-05-20 Thread Phil Race
On Mon, 13 May 2024 10:49:30 GMT, Maurizio Cimadamore wrote: >> Maurizio Cimadamore has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Address review comments > > make/conf/module-loader-map.conf line 105: > >> 103: java.smartcardio \

Re: RFR: 8331605: jdk/test/lib/TestMutuallyExclusivePlatformPredicates.java test failure

2024-05-02 Thread Phil Race
On Thu, 2 May 2024 21:05:38 GMT, Alexander Zvegintsev wrote: > Trivial fix. Marked as reviewed by prr (Reviewer). OK. I see. The problem is that the test is out of sync with the actual usage of Platform. Arguably isOnWayland() and all these others should be in some OTHER class entirely. Some

Re: RFR: 8331605: jdk/test/lib/TestMutuallyExclusivePlatformPredicates.java test failure

2024-05-02 Thread Phil Race
On Thu, 2 May 2024 21:05:38 GMT, Alexander Zvegintsev wrote: > Trivial fix. I see you added test.lib.Platform.isOnWayland() in this PR https://github.com/openjdk/jdk/pull/18995/files#diff-a1fe81399728999601f16ae9aaf5caae27f009c394377d2cd86c71f6d5e0e54c So, that helps me understand why it is a

Re: RFR: 8331605: jdk/test/lib/TestMutuallyExclusivePlatformPredicates.java test failure

2024-05-02 Thread Phil Race
On Thu, 2 May 2024 21:05:38 GMT, Alexander Zvegintsev wrote: > Trivial fix. I'd love to approve this but could you please explain what this is about ? I see the failure log in the bug report but I am none the wiser. Why exactly is this a problem ? - PR Comment: https://git.openjd

Re: RFR: 8303689: javac -Xlint could/should report on "dangling" doc comments [v10]

2024-04-26 Thread Phil Race
On Fri, 26 Apr 2024 16:04:09 GMT, Jonathan Gibbons wrote: >> Please review the updates to support a proposed new >> `-Xlint:dangling-doc-comments` option. >> >> The work can be thought of as in 3 parts: >> >> 1. An update to the `javac` internal class `DeferredLintHandler` so that it >> is po

Re: RFR: 8314592: Add shortcut to SymbolLookup::find [v6]

2024-04-18 Thread Phil Race
On Thu, 18 Apr 2024 11:32:13 GMT, Per Minborg wrote: >> While `SymbolLookup` correctly uses an `Optional` return to denote whether a >> symbol has been found by the lookup or not (which enables composition of >> symbol lookups), many clients end up just calling `Optional::get`, or >> `Optional

Re: RFR: 8325163: Enable -Wpedantic on clang [v2]

2024-02-16 Thread Phil Race
On Mon, 5 Feb 2024 10:58:17 GMT, Magnus Ihse Bursie wrote: >> Inspired by (the later backed-out) >> [JDK-8296115](https://bugs.openjdk.org/browse/JDK-8296115), I propose to >> enable `-Wpedantic` for clang. This has already found some irregularities in >> the code, like mistakenly using `#impo

Re: RFR: 8325950: Make sure all files in the JDK pass jcheck

2024-02-15 Thread Phil Race
On Thu, 15 Feb 2024 12:19:31 GMT, Magnus Ihse Bursie wrote: > Since jcheck only checks file in a commit, there is a possibility of us > getting files in the repository that would not be accepted by jcheck. This > can happen when extending the set of files checked by jcheck, or if jcheck > chan

Integrated: 8320608: Many jtreg printing tests are missing the @printer keyword

2023-11-30 Thread Phil Race
On Wed, 22 Nov 2023 19:26:40 GMT, Phil Race wrote: > Many printing tests do not have the @printer keyword. This adds them to those > that need it. > I also found one test that has nothing to do with printing in the print > folder and moved it out. This pull request has now bee

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v3]

2023-11-30 Thread Phil Race
On Thu, 30 Nov 2023 19:50:00 GMT, Sergey Bylokhov wrote: > probably we can link this from our wiki page where we describe the usage of > keywords?: > https://wiki.openjdk.org/display/ClientLibs/Automated+client+GUI+testing+system+set+up+requirements Good idea, once this is pushed, I'll add th

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v3]

2023-11-30 Thread Phil Race
> Many printing tests do not have the @printer keyword. This adds them to those > that need it. > I also found one test that has nothing to do with printing in the print > folder and moved it out. Phil Race has updated the pull request incrementally with one additional commit si

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v2]

2023-11-30 Thread Phil Race
On Thu, 30 Nov 2023 17:08:21 GMT, Alexey Ivanov wrote: >> Phil Race has updated the pull request incrementally with one additional >> commit since the last revision: >> >> 8320608 > > test/jdk/java/awt/print/PrinterJob/EmptyFill.java line 72: >

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v2]

2023-11-30 Thread Phil Race
On Thu, 30 Nov 2023 15:41:28 GMT, Alexey Ivanov wrote: >> "Should not" is strong. Why ? There's no requirement do to this even though >> you can. >> https://openjdk.org/jtreg/faq.html#can-i-use-the-author-run-etc.-tags-in-other-files > > That's the reason why I prefer you keep the `@run` tag in

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v2]

2023-11-30 Thread Phil Race
On Thu, 30 Nov 2023 15:59:29 GMT, Alexey Ivanov wrote: >> Phil Race has updated the pull request incrementally with one additional >> commit since the last revision: >> >> 8320608 > > test/jdk/java/awt/print/PageFormat/SmallPaperPrinting.java line 73: > &g

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword [v2]

2023-11-27 Thread Phil Race
> Many printing tests do not have the @printer keyword. This adds them to those > that need it. > I also found one test that has nothing to do with printing in the print > folder and moved it out. Phil Race has updated the pull request incrementally with one additional commit si

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword

2023-11-27 Thread Phil Race
On Thu, 23 Nov 2023 20:39:50 GMT, Alexey Ivanov wrote: >> test/jdk/java/awt/print/PageFormat/SetOrient.java line 28: >> >>> 26: * @summary Confirm that the clip and transform of the Graphics2D is >>> 27: * affected by the landscape orientation of the PageFormat. >>> 28: */ >> >> Sin

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword

2023-11-27 Thread Phil Race
On Thu, 23 Nov 2023 07:02:54 GMT, Alan Bateman wrote: >> Many printing tests do not have the @printer keyword. This adds them to >> those that need it. >> I also found one test that has nothing to do with printing in the print >> folder and moved it out. > > test/jdk/TEST.ROOT line 15: > >> 13

Re: RFR: 8320608: Many jtreg printing tests are missing the @printer keyword

2023-11-27 Thread Phil Race
On Thu, 23 Nov 2023 11:10:35 GMT, Alexey Ivanov wrote: >> Many printing tests do not have the @printer keyword. This adds them to >> those that need it. >> I also found one test that has nothing to do with printing in the print >> folder and moved it out. > > test/jdk/java/awt/PrintJob/EdgeTest

RFR: 8320608: Many jtreg printing tests are missing the @printer keyword

2023-11-22 Thread Phil Race
Many printing tests do not have the @printer keyword. This adds them to those that need it. I also found one test that has nothing to do with printing in the print folder and moved it out. - Commit messages: - 8320608 Changes: https://git.openjdk.org/jdk/pull/16785/files Webrev:

Integrated: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-11-21 Thread Phil Race
On Tue, 29 Aug 2023 22:04:40 GMT, Phil Race wrote: > 8318364: Add an FFM-based implementation of harfbuzz OpenType layout This pull request has now been integrated. Changeset: f69e6653 Author: Phil Race URL: https://git.openjdk.org/jdk/commit/f69e6653f86a7dd781db6c8523f114c0d3f7c

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v7]

2023-11-20 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8318364 - Changes: - all: https://git.openjdk.org/jdk/pull/15476/files - new: ht

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-20 Thread Phil Race
On Thu, 16 Nov 2023 13:48:38 GMT, Prasanta Sadhukhan wrote: >> Phil Race has updated the pull request incrementally with one additional >> commit since the last revision: >> >> indentation > > src/java.desktop/share/classes/sun/font/HBShaper.java line 628: &g

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v6]

2023-11-16 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8318364 - Changes: - all: https://git.openjdk.org/jdk/pull/15476/files - new: ht

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-16 Thread Phil Race
On Wed, 15 Nov 2023 15:06:55 GMT, Jayathirth D V wrote: >> Phil Race has updated the pull request incrementally with one additional >> commit since the last revision: >> >> indentation > > src/java.desktop/share/classes/sun/font/HBShaper.java line 66: > >

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-16 Thread Phil Race
On Thu, 16 Nov 2023 19:35:53 GMT, Jorn Vernee wrote: > > > > > layoutCnt=16000 total=193ms <<< app fully displayed > > > > > vs > > > > > layoutCnt=16000 total=453ms <<< app fully displayed > > > > > > > > > > > > It looks strange that 16000 calls are not enough to warmup, and the > > > > diff

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v5]

2023-11-16 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 21 commits: - Merge remote-tracking branch 'upstream/master' into harfbuzz_pa

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-15 Thread Phil Race
On Wed, 15 Nov 2023 15:52:43 GMT, Jayathirth D V wrote: >> Phil Race has updated the pull request incrementally with one additional >> commit since the last revision: >> >> indentation > > src/java.desktop/share/classes/sun/font/HBShaper.java line 142: >

Re: RFR: JDK-8313764: Offer JVM HS functionality to shared lib load operations done by the JDK codebase [v2]

2023-11-15 Thread Phil Race
On Wed, 23 Aug 2023 15:18:03 GMT, Matthias Baesken wrote: >> Currently there is a number of functionality that would be interesting to >> have for shared lib load operations in the JDK C code. >> Some examples : >> Events::log_dll_message for hs-err files reporting >> JFR event NativeLibraryLoad

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-06 Thread Phil Race
On Mon, 6 Nov 2023 23:58:11 GMT, Sergey Bylokhov wrote: > > So we have somewhere around a fixed 125ms startup cost for the FFM case - > > as measured on my Mac, > > but only 35-40ms of that is attributable to the specific needs of layout. > > That looks unfortunate. I guess if we will start to

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-11-06 Thread Phil Race
On Mon, 6 Nov 2023 18:52:05 GMT, Sergey Bylokhov wrote: > Since we plan to import it into jdk22, do you have some performance data to > share? any positive or negative effects of this migration? There's three phases - (1) startup, (2) warmup and (3) warmed up performance. JNI has minimal star

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v4]

2023-10-25 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request incrementally with one additional commit since the last revision: indentation - Changes: - all: https://git.openjdk.org/jdk/pull/15476/files - new: ht

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v3]

2023-10-20 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request incrementally with one additional commit since the last revision: Use new arrayElementVarHandle method - Changes: - all: https://git.openjdk.org/jdk/pull/15476/fi

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout [v2]

2023-10-20 Thread Phil Race
> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout Phil Race has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 18 commits: - Merge remote-tracking branch 'upstream/master' into harfbuzz_panama Me

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Tue, 29 Aug 2023 22:04:40 GMT, Phil Race wrote: > 8318364: Add an FFM-based implementation of harfbuzz OpenType layout That's interesting. As soon as this went RFR, skara started to send all the emails from several weeks of already resolved discussions but with a current timestamp,

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Wed, 18 Oct 2023 06:16:15 GMT, Jorn Vernee wrote: >>> > I'm unclear why it is "better". It seems more obscure to me. >>> >>> Ok. I think it's better because it doesn't require creating a maximum size >>> sequence layout in order to then make a var handle out of, which is a bit >>> of a hack

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Tue, 29 Aug 2023 22:04:40 GMT, Phil Race wrote: > 8318364: Add an FFM-based implementation of harfbuzz OpenType layout I've added a test, which although it does not check the rendering is correct, it checks that the rendering would be identical in both the JNI and FFM cases. So

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Wed, 18 Oct 2023 03:43:15 GMT, Jorn Vernee wrote: > > I'm unclear why it is "better". It seems more obscure to me. > > Ok. I think it's better because it doesn't require creating a maximum size > sequence layout in order to then make a var handle out of, which is a bit of > a hack IMO. One

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Tue, 17 Oct 2023 11:50:20 GMT, Jorn Vernee wrote: >> 8318364: Add an FFM-based implementation of harfbuzz OpenType layout > > src/java.desktop/share/classes/sun/font/HBShaper.java line 310: > >> 308: SequenceLayout glyphInfosLayout = >> MemoryLayout.sequenceLayout(maxinfo, GlyphInfoL

Re: RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
On Wed, 30 Aug 2023 02:55:34 GMT, Sergey Bylokhov wrote: > @prrace did you check how this change affects the performance, especially > startup? I have experimented with Panama for littlecms: > https://bugs.openjdk.org/browse/JDK-8313344 and found that the biggest issue > is a cold start, 8 ms

RFR: 8318364: Add an FFM-based implementation of harfbuzz OpenType layout

2023-10-18 Thread Phil Race
8318364: Add an FFM-based implementation of harfbuzz OpenType layout - Commit messages: - remove tailing white space - use scaling - Fix windows build, remove perf. logging - Add test, fix bug - use allocateFrom - add offset param - suppressed restricted warnings, now builds bu

Re: RFR: JDK-8313764: Offer JVM HS functionality to shared lib load operations done by the JDK codebase

2023-08-14 Thread Phil Race
On Mon, 14 Aug 2023 07:48:00 GMT, Matthias Baesken wrote: > Currently there is a number of functionality that would be interesting to > have for shared lib load operations in the JDK C code. > Some examples : > Events::log_dll_message for hs-err files reporting > JFR event NativeLibraryLoad > Th

Re: RFR: 8310999: Add @since info in jdk.jsobject files [v2]

2023-07-05 Thread Phil Race
On Wed, 5 Jul 2023 16:20:07 GMT, Roger Riggs wrote: >> Source code cleanup. >> Add @since, remove unused imports and remove unnecessary SuppressWarnings of >> deprecation. > > Roger Riggs has updated the pull request incrementally with one additional > commit since the last revision: > > Rem

Re: RFR: 8310999: Add @since info in jdk.jsobject files

2023-07-05 Thread Phil Race
On Wed, 5 Jul 2023 14:51:31 GMT, Roger Riggs wrote: > Source code cleanup. > Add @since, remove unused imports and remove unnecessary SuppressWarnings of > deprecation. unless my eyes deceive me the suppresswarnings is still present. - Changes requested by prr (Reviewer). PR Revi

Re: RFR: 8310187: Improve Generational ZGC jtreg testing [v3]

2023-06-20 Thread Phil Race
On Mon, 19 Jun 2023 06:55:52 GMT, Axel Boldt-Christmas wrote: >> The current implementation for testing generational ZGC with jtreg is >> implemented with a filter on the mode flag `ZGenerational`. Because of this >> only environments which set this flag explicitly will run most of the tests.

Re: RFR: 8308780: Fix the Java Integer types on Windows [v4]

2023-06-15 Thread Phil Race
On Thu, 1 Jun 2023 11:49:24 GMT, Julian Waters wrote: >> On Windows, the basic Java Integer types are defined as long and __int64 >> respectively. In particular, the former is rather problematic since it >> breaks compilation as the Visual C++ becomes stricter and more compliant >> with every

Re: RFR: 8308780: Fix the Java Integer types on Windows [v4]

2023-06-01 Thread Phil Race
On Thu, 1 Jun 2023 11:49:24 GMT, Julian Waters wrote: >> On Windows, the basic Java Integer types are defined as long and __int64 >> respectively. In particular, the former is rather problematic since it >> breaks compilation as the Visual C++ becomes stricter and more compliant >> with every

Re: RFR: JDK-8308288: Fix xlc17 clang warnings in shared code [v2]

2023-05-31 Thread Phil Race
On Fri, 26 May 2023 08:31:46 GMT, JoKern65 wrote: >> When using the new xlc17 compiler (based on a recent clang) to build OpenJDk >> on AIX , we run into various "warnings as errors". >> Some of those are in shared codebase and could be addressed by small >> adjustments. >> A lot of those chang

Re: RFR: 8308286 Fix clang warnings in linux code

2023-05-22 Thread Phil Race
On Wed, 17 May 2023 12:28:47 GMT, Artem Semenov wrote: > When using the clang compiler to build OpenJDk on Linux, we encounter various > "warnings as errors". > They can be fixed with small changes. I don't like this approach at all. if github had a "reject" button I'd be pushing it now. updat

Re: RFR: 8303796: Optionally build fully statically linked JDK image

2023-04-28 Thread Phil Race
On Fri, 28 Apr 2023 01:03:28 GMT, Jiangli Zhou wrote: > Initial implementation for supporting building a fully statically linked > (with a desired set of JDK native libraries and libjvm) Java launcher > executable, which is named as 'javastatic'. > > In this PR, the support is only added for t

Re: RFR: 8304717: Declaration aliasing between boolean and jboolean is wrong [v3]

2023-04-06 Thread Phil Race
On Fri, 31 Mar 2023 05:57:01 GMT, Julian Waters wrote: >> A couple of spots wrongly refer to boolean and jboolean as the same thing. >> While this does still compile thanks to a happy accident and implicit >> conversions, they are not the same at all, and should be fixed before a >> future com

Re: RFR: 8304915: Create jdk.internal.util.Architecture enum and apply [v7]

2023-04-06 Thread Phil Race
On Thu, 6 Apr 2023 19:25:19 GMT, Roger Riggs wrote: >> Define an internal jdk.internal.util.Architecture enumeration and static >> methods to replace uses of the system property `os.arch`. >> The enumeration values are defined to match those used in the build. >> The initial values are: `X64, X8

Re: RFR: 8303018: Unicode Emoji Properties

2023-03-13 Thread Phil Race
On Mon, 13 Mar 2023 21:16:24 GMT, Naoto Sato wrote: > Proposing accessor methods to Emoji properties defined in [Unicode Technical > Standard #51](https://unicode.org/reports/tr51/) in `java.lang.Character` > class. This is per a request from the client group, as well as refining the > current

Re: RFR: 8303480: Miscellaneous fixes to mostly invisible doc comments

2023-03-02 Thread Phil Race
On Thu, 2 Mar 2023 12:03:44 GMT, Pavel Rappo wrote: > Please review this superficial documentation cleanup that was triggered by > unrelated analysis of doc comments in JDK API. > > The only effect that this multi-area PR has on the JDK API Documentation > (i.e. the observable effect on the ge

Re: [jdk20] RFR: 8300719: JDK 20 RDP2 L10n resource files update [v2]

2023-01-24 Thread Phil Race
On Tue, 24 Jan 2023 22:12:26 GMT, Damon Nguyen wrote: >> Open l10n drop. Files have been updated with translated versions. Whitespace >> tool has been ran on files. >> All tests passed > > Damon Nguyen has updated the pull request incrementally with one additional > commit since the last revisi

Re: RFR: 8300169: Build failure with clang-15

2023-01-17 Thread Phil Race
On Sat, 14 Jan 2023 14:28:32 GMT, Jie Fu wrote: > Hi all, > > Please review the fix for the build failure with clang-15. > > 1. -Wbitwise-instead-of-logical > >1) src/hotspot/share/oops/generateOopMap.cpp <--- fixed the > warning >2) src/hotspot/share/runtime/notificationThre

Re: RFR: 8300169: Build failure with clang-15

2023-01-17 Thread Phil Race
On Tue, 17 Jan 2023 13:35:25 GMT, Kevin Rushforth wrote: >>> Normally, such changes in third-party libraries need to be done upstream, >>> and not locally. @prrace can confirm. >> >> Thanks @kevinrushforth for your review. >> >> Yes, it had been fixed in the upstream and I just follow it. >> P

  1   2   >