From azvegint at openjdk.org Mon Dec 2 00:58:46 2024 From: azvegint at openjdk.org (Alexander Zvegintsev) Date: Mon, 2 Dec 2024 00:58:46 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v2] In-Reply-To: References: Message-ID: <7sYuojWQDsIRMswxvYS1uqj5_NepvjYfZjXT3Q7sTgQ=.817db01a-3ea3-4d3c-a7c5-d57b8be35c51@github.com> On Fri, 29 Nov 2024 01:04:32 GMT, Alexander Zvegintsev wrote: >> Phil Race has updated the pull request incrementally with one additional commit since the last revision: >> >> 8345143 > > src/java.desktop/share/classes/javax/swing/Popup.java line 247: > >> 245: // Try to set "always-on-top" for the popup window. >> 246: // Applets usually don't have sufficient permissions to do it. >> 247: // In this case simply ignore the exception. > > Suggestion: This can still be updated. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1865083798 From prr at openjdk.org Mon Dec 2 04:23:46 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 2 Dec 2024 04:23:46 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v3] In-Reply-To: <7sYuojWQDsIRMswxvYS1uqj5_NepvjYfZjXT3Q7sTgQ=.817db01a-3ea3-4d3c-a7c5-d57b8be35c51@github.com> References: <7sYuojWQDsIRMswxvYS1uqj5_NepvjYfZjXT3Q7sTgQ=.817db01a-3ea3-4d3c-a7c5-d57b8be35c51@github.com> Message-ID: On Mon, 2 Dec 2024 00:55:55 GMT, Alexander Zvegintsev wrote: >> src/java.desktop/share/classes/javax/swing/Popup.java line 247: >> >>> 245: // Try to set "always-on-top" for the popup window. >>> 246: // Applets usually don't have sufficient permissions to do it. >>> 247: // In this case simply ignore the exception. >> >> Suggestion: > > This can still be updated. fixed ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1865204366 From prr at openjdk.org Mon Dec 2 04:23:45 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 2 Dec 2024 04:23:45 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v3] In-Reply-To: References: Message-ID: <60yT3WANw9AZv4R8kKUPtf8bziCriK_I2-nk6Qn0jCA=.31992c2f-c8a2-497e-92ee-2f44c50caecc@github.com> > Remove SecurityManager related code in the desktop module that is not covered by other PRs Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8345143 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22424/files - new: https://git.openjdk.org/jdk/pull/22424/files/a02cecb4..17302404 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=01-02 Stats: 3 lines in 1 file changed: 0 ins; 3 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/22424.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22424/head:pull/22424 PR: https://git.openjdk.org/jdk/pull/22424 From azvegint at openjdk.org Mon Dec 2 04:40:42 2024 From: azvegint at openjdk.org (Alexander Zvegintsev) Date: Mon, 2 Dec 2024 04:40:42 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v3] In-Reply-To: <60yT3WANw9AZv4R8kKUPtf8bziCriK_I2-nk6Qn0jCA=.31992c2f-c8a2-497e-92ee-2f44c50caecc@github.com> References: <60yT3WANw9AZv4R8kKUPtf8bziCriK_I2-nk6Qn0jCA=.31992c2f-c8a2-497e-92ee-2f44c50caecc@github.com> Message-ID: On Mon, 2 Dec 2024 04:23:45 GMT, Phil Race wrote: >> Remove SecurityManager related code in the desktop module that is not covered by other PRs > > Phil Race has updated the pull request incrementally with one additional commit since the last revision: > > 8345143 Marked as reviewed by azvegint (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22424#pullrequestreview-2471726576 From jwaters at openjdk.org Mon Dec 2 12:05:43 2024 From: jwaters at openjdk.org (Julian Waters) Date: Mon, 2 Dec 2024 12:05:43 GMT Subject: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] In-Reply-To: References: Message-ID: On Thu, 31 Oct 2024 05:43:11 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 unused warnings and addressed all of them by commenting out the code as appropriate. I am confident that in many cases this simplistic approach of commenting out code does not fix the underlying issue, and the warning actually found a bug that should be fixed. In these instances, I will be aiming to fix these bugs with help from reviewers, so I recommend anyone reviewing who knows more about the code than I do to see whether there is indeed a bug that needs fixing in a different way than what I did > > Julian Waters has updated the pull request incrementally with one additional commit since the last revision: > > Remove the got local Keep it open Skara, I'm waiting for the other Pull Requests to be approved so I can do them all at once ------------- PR Comment: https://git.openjdk.org/jdk/pull/21654#issuecomment-2511352014 From naoto at openjdk.org Mon Dec 2 17:08:56 2024 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 2 Dec 2024 17:08:56 GMT Subject: RFR: 8343788: Provide means to alter lib/tzmappings entries on Windows In-Reply-To: References: Message-ID: <-eF98J84vSxXjEor6sQJwtj9qoywQX-5HimNe7YpcRI=.e00ba669-0c3e-4ac6-8aa4-d3eb406c9d5e@github.com> On Tue, 19 Nov 2024 17:31:42 GMT, Naoto Sato wrote: > Windows Java runtime has a mapping file /lib/tzmappings which maps Windows time zones to Java's time zones. The file is generated based on CLDR's windowsZones.xml, but in rare occasions, its update is out of sync with Windows updates. This enhancement is to address those discrepancies for the time being (till CLDR/Windows are in sync). This change will also address zone mapping discrepancies in the update releases where CLDR versions stay the same. Thanks for the review! ------------- PR Comment: https://git.openjdk.org/jdk/pull/22250#issuecomment-2512177124 From naoto at openjdk.org Mon Dec 2 17:08:57 2024 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 2 Dec 2024 17:08:57 GMT Subject: Integrated: 8343788: Provide means to alter lib/tzmappings entries on Windows In-Reply-To: References: Message-ID: On Tue, 19 Nov 2024 17:31:42 GMT, Naoto Sato wrote: > Windows Java runtime has a mapping file /lib/tzmappings which maps Windows time zones to Java's time zones. The file is generated based on CLDR's windowsZones.xml, but in rare occasions, its update is out of sync with Windows updates. This enhancement is to address those discrepancies for the time being (till CLDR/Windows are in sync). This change will also address zone mapping discrepancies in the update releases where CLDR versions stay the same. This pull request has now been integrated. Changeset: 352201dd Author: Naoto Sato URL: https://git.openjdk.org/jdk/commit/352201ddecb048fe41bdf68d775a0a6cb2080122 Stats: 54 lines in 2 files changed: 53 ins; 0 del; 1 mod 8343788: Provide means to alter lib/tzmappings entries on Windows Reviewed-by: joehw ------------- PR: https://git.openjdk.org/jdk/pull/22250 From prr at openjdk.org Mon Dec 2 18:49:58 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 2 Dec 2024 18:49:58 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v4] In-Reply-To: References: Message-ID: > Remove SecurityManager related code in the desktop module that is not covered by other PRs Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8345143 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22424/files - new: https://git.openjdk.org/jdk/pull/22424/files/17302404..c4810ca7 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=03 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=02-03 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22424.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22424/head:pull/22424 PR: https://git.openjdk.org/jdk/pull/22424 From prr at openjdk.org Mon Dec 2 18:57:58 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 2 Dec 2024 18:57:58 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v5] In-Reply-To: References: Message-ID: > Remove SecurityManager related code in the desktop module that is not covered by other PRs Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8345143 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22424/files - new: https://git.openjdk.org/jdk/pull/22424/files/c4810ca7..89c21e97 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=03-04 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22424.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22424/head:pull/22424 PR: https://git.openjdk.org/jdk/pull/22424 From prr at openjdk.org Mon Dec 2 19:01:06 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 2 Dec 2024 19:01:06 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: References: Message-ID: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> > Remove SecurityManager related code in the desktop module that is not covered by other PRs Phil Race has updated the pull request incrementally with one additional commit since the last revision: 8345143 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22424/files - new: https://git.openjdk.org/jdk/pull/22424/files/89c21e97..046edd8c Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=05 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22424&range=04-05 Stats: 3 lines in 1 file changed: 0 ins; 2 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22424.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22424/head:pull/22424 PR: https://git.openjdk.org/jdk/pull/22424 From rriggs at openjdk.org Mon Dec 2 20:16:54 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 20:16:54 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base Message-ID: Remove sun/security/action/GetPropertyAction.java and all uses. Dependent on PR#22418 ------------- Depends on: https://git.openjdk.org/jdk/pull/22418 Commit messages: - 8345325: SM cleanup of GetPropertyAction in java.base Changes: https://git.openjdk.org/jdk/pull/22497/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345325 Stats: 184 lines in 10 files changed: 0 ins; 174 del; 10 mod Patch: https://git.openjdk.org/jdk/pull/22497.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22497/head:pull/22497 PR: https://git.openjdk.org/jdk/pull/22497 From lancea at openjdk.org Mon Dec 2 20:21:39 2024 From: lancea at openjdk.org (Lance Andersen) Date: Mon, 2 Dec 2024 20:21:39 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base In-Reply-To: References: Message-ID: <4g-Q8_Y2ArAR3aXJZKfoko_qoDiTYCel4-WV5eb1pBc=.e38e828d-bb11-423e-85db-0e21ad0ae956@github.com> On Mon, 2 Dec 2024 20:12:39 GMT, Roger Riggs wrote: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 Changes Look Good Roger ------------- Marked as reviewed by lancea (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2473825040 From alanb at openjdk.org Mon Dec 2 20:21:40 2024 From: alanb at openjdk.org (Alan Bateman) Date: Mon, 2 Dec 2024 20:21:40 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:12:39 GMT, Roger Riggs wrote: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 src/java.base/share/classes/java/lang/invoke/MethodHandleNatives.java line 710: > 708: > 709: static { > 710: Properties props = GetPropertyAction.privilegedGetProperties(); This is probably the last usage of Properties. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1866556255 From naoto at openjdk.org Mon Dec 2 20:31:38 2024 From: naoto at openjdk.org (Naoto Sato) Date: Mon, 2 Dec 2024 20:31:38 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:12:39 GMT, Roger Riggs wrote: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 LGTM ------------- Marked as reviewed by naoto (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2473841217 From rriggs at openjdk.org Mon Dec 2 20:31:39 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 20:31:39 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:19:23 GMT, Alan Bateman wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > src/java.base/share/classes/java/lang/invoke/MethodHandleNatives.java line 710: > >> 708: >> 709: static { >> 710: Properties props = GetPropertyAction.privilegedGetProperties(); > > This is probably the last usage of Properties. Yes, with Sean's changes in #22418, GetPropertyAction et.al. is deleted. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1866566036 From rriggs at openjdk.org Mon Dec 2 20:47:16 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 20:47:16 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 Roger Riggs has updated the pull request incrementally with two additional commits since the last revision: - Remove unused import of Properties - Update copyrights Remove jdk/sun/security/action/Generify test ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22497/files - new: https://git.openjdk.org/jdk/pull/22497/files/683b008e..d6586f9b Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=00-01 Stats: 52 lines in 5 files changed: 0 ins; 49 del; 3 mod Patch: https://git.openjdk.org/jdk/pull/22497.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22497/head:pull/22497 PR: https://git.openjdk.org/jdk/pull/22497 From mchung at openjdk.org Mon Dec 2 20:47:16 2024 From: mchung at openjdk.org (Mandy Chung) Date: Mon, 2 Dec 2024 20:47:16 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: <9ZOAyA1fSdjH22fEOUPJq9_pvi9QQYv5vIGD5_DxFfA=.d900b0aa-0d24-4021-92ab-708cbb95b29e@github.com> On Mon, 2 Dec 2024 20:44:05 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request incrementally with two additional commits since the last revision: > > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test LGTM ------------- Marked as reviewed by mchung (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2473865834 From eirbjo at openjdk.org Mon Dec 2 20:47:16 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Mon, 2 Dec 2024 20:47:16 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: <1Xm5gSud354bl56Yd-ccM_WHG0t42zEECqBWOzXQRzU=.8152e918-1129-4a64-a691-b2adefd6f40a@github.com> On Mon, 2 Dec 2024 20:28:13 GMT, Roger Riggs wrote: >> src/java.base/share/classes/java/lang/invoke/MethodHandleNatives.java line 710: >> >>> 708: >>> 709: static { >>> 710: Properties props = GetPropertyAction.privilegedGetProperties(); >> >> This is probably the last usage of Properties. > > Yes, with Sean's changes in #22418, GetPropertyAction et.al. is deleted. @RogerRiggs Alan may have referred to the import of `java.util.Properties`. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1866579197 From rriggs at openjdk.org Mon Dec 2 20:47:16 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 20:47:16 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: <1Xm5gSud354bl56Yd-ccM_WHG0t42zEECqBWOzXQRzU=.8152e918-1129-4a64-a691-b2adefd6f40a@github.com> References: <1Xm5gSud354bl56Yd-ccM_WHG0t42zEECqBWOzXQRzU=.8152e918-1129-4a64-a691-b2adefd6f40a@github.com> Message-ID: On Mon, 2 Dec 2024 20:40:23 GMT, Eirik Bj?rsn?s wrote: >> Yes, with Sean's changes in #22418, GetPropertyAction et.al. is deleted. > > @RogerRiggs Alan may have referred to the import of `java.util.Properties`. Right, thanks ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1866581277 From azvegint at openjdk.org Mon Dec 2 21:08:46 2024 From: azvegint at openjdk.org (Alexander Zvegintsev) Date: Mon, 2 Dec 2024 21:08:46 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> References: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> Message-ID: On Mon, 2 Dec 2024 19:01:06 GMT, Phil Race wrote: >> Remove SecurityManager related code in the desktop module that is not covered by other PRs > > Phil Race has updated the pull request incrementally with one additional commit since the last revision: > > 8345143 Marked as reviewed by azvegint (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22424#pullrequestreview-2473924924 From mchung at openjdk.org Mon Dec 2 21:15:42 2024 From: mchung at openjdk.org (Mandy Chung) Date: Mon, 2 Dec 2024 21:15:42 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:47:16 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request incrementally with two additional commits since the last revision: > > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test Marked as reviewed by mchung (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2473937851 From mullan at openjdk.org Mon Dec 2 22:05:40 2024 From: mullan at openjdk.org (Sean Mullan) Date: Mon, 2 Dec 2024 22:05:40 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:47:16 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request incrementally with two additional commits since the last revision: > > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test This includes a lot of changes already integrated in 8344397. Is that normal? ------------- PR Comment: https://git.openjdk.org/jdk/pull/22497#issuecomment-2513031346 From liach at openjdk.org Mon Dec 2 22:35:38 2024 From: liach at openjdk.org (Chen Liang) Date: Mon, 2 Dec 2024 22:35:38 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v2] In-Reply-To: References: Message-ID: <14R-g7fDTxZCTaMkyOs_SbH8KOMUmimu4yz7uEpe8Qo=.2873489c-d6de-4b7d-a3fc-1cb1375ff51f@github.com> On Mon, 2 Dec 2024 22:02:54 GMT, Sean Mullan wrote: > This includes a lot of changes already integrated in 8344397. Is that normal? I believe this is due to GitHub's diff rendering when it detects a merge conflict. It should go away once the conflict is fixed. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22497#issuecomment-2513105799 From rriggs at openjdk.org Mon Dec 2 22:51:55 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 22:51:55 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: - Merge branch 'master' into 8345325-sm-remove-getpropertyaction - Remove unused import of Properties - Update copyrights Remove jdk/sun/security/action/Generify test - 8345325: SM cleanup of GetPropertyAction in java.base Remove use of GetPropertyAction Remove sun/security/action/GetPropertyAction.java - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp methods to sun.security.util.SecurityProperties and rename them. - Replace remaining calls to SecurityProperties.privilegedGetOverridable() with SecurityProperties.getOverridableProperty() and remove privilegedGetOverridable(). - Merge - Remove doPrivileged calls. - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. - Remove permission text from comments in Provider.java. - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 ------------- Changes: https://git.openjdk.org/jdk/pull/22497/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=02 Stats: 236 lines in 11 files changed: 0 ins; 223 del; 13 mod Patch: https://git.openjdk.org/jdk/pull/22497.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22497/head:pull/22497 PR: https://git.openjdk.org/jdk/pull/22497 From rriggs at openjdk.org Mon Dec 2 22:54:42 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 2 Dec 2024 22:54:42 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 22:51:55 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Merge branch 'master' into 8345325-sm-remove-getpropertyaction > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test > - 8345325: SM cleanup of GetPropertyAction in java.base > Remove use of GetPropertyAction > Remove sun/security/action/GetPropertyAction.java > - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. > Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp > methods to sun.security.util.SecurityProperties and rename them. > - Replace remaining calls to SecurityProperties.privilegedGetOverridable() > with SecurityProperties.getOverridableProperty() and remove > privilegedGetOverridable(). > - Merge > - Remove doPrivileged calls. > - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. > - Remove permission text from comments in Provider.java. > - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 The merge of master after integrating 8344397 looks to have resolved conflicts and only the intended changes remain. I'll run a CI build to confirm tier1-3. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22497#issuecomment-2513145496 From darcy at openjdk.org Mon Dec 2 23:02:41 2024 From: darcy at openjdk.org (Joe Darcy) Date: Mon, 2 Dec 2024 23:02:41 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v4] In-Reply-To: References: Message-ID: On Thu, 21 Nov 2024 06:53:58 GMT, Justin Lu wrote: >> Please review this PR and corresponding CSR which includes a wide range of specification improvements for java.util.Locale. See the CSR for further detail. Other changes/suggestions are welcomed to be included as part of this change. >> >> APIDiff: https://cr.openjdk.org/~jlu/8341923_apidiff/java.base/java/util/Locale.html >> Javadoc: https://cr.openjdk.org/~jlu/api/java.base/java/util/Locale.html > > Justin Lu has updated the pull request incrementally with one additional commit since the last revision: > > reflect review src/java.base/share/classes/java/util/Locale.java line 76: > 74: * or cultural region. An API that requires a {@code Locale} to perform > 75: * its task is locale-sensitive and uses the {@code Locale} > 76: * to tailor information for the user. These locale-sensitive APIs Either as part of this change or in follow-up work, please consider defining a user-index term for "locale -sensitive". ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22192#discussion_r1866741419 From honkar at openjdk.org Mon Dec 2 23:18:43 2024 From: honkar at openjdk.org (Harshitha Onkar) Date: Mon, 2 Dec 2024 23:18:43 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> References: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> Message-ID: On Mon, 2 Dec 2024 19:01:06 GMT, Phil Race wrote: >> Remove SecurityManager related code in the desktop module that is not covered by other PRs > > Phil Race has updated the pull request incrementally with one additional commit since the last revision: > > 8345143 LGTM src/java.desktop/share/classes/javax/swing/DefaultListCellRenderer.java line 108: > 106: if (System.getSecurityManager() != null) { > 107: if (border != null) return border; > 108: return SAFE_NO_FOCUS_BORDER; Changes looks good. SAFE_NO_FOCUS_BORDER no longer used. ------------- Marked as reviewed by honkar (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22424#pullrequestreview-2474123132 PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1866744305 From honkar at openjdk.org Mon Dec 2 23:39:44 2024 From: honkar at openjdk.org (Harshitha Onkar) Date: Mon, 2 Dec 2024 23:39:44 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> References: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> Message-ID: On Mon, 2 Dec 2024 19:01:06 GMT, Phil Race wrote: >> Remove SecurityManager related code in the desktop module that is not covered by other PRs > > Phil Race has updated the pull request incrementally with one additional commit since the last revision: > > 8345143 test/jdk/lib/client/ExtendedRobot.java line 64: > 62: // syncDelay = AccessController.doPrivileged(new GetIntegerAction("java.awt.robotdelay", DEFAULT_SYNC_DELAY)); > 63: //} > 64: Not related to this PR changes but since ExtendedRobot was mentioned here, I went through Robot.java and it has few SecurityException in javadoc [(as here)](https://github.com/openjdk/jdk/blob/db85090553ab14a84c3ed0a2604dd56c5b6e6982/src/java.desktop/share/classes/java/awt/Robot.java#L506C1-L507C43). Will changes to Robot.java be handled as separate PR + CSR ? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1866768907 From prr at openjdk.org Tue Dec 3 00:15:48 2024 From: prr at openjdk.org (Phil Race) Date: Tue, 3 Dec 2024 00:15:48 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: References: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> Message-ID: On Mon, 2 Dec 2024 23:37:03 GMT, Harshitha Onkar wrote: > Not related to this PR changes but since ExtendedRobot was mentioned here, I went through Robot.java and it has few SecurityException in javadoc [(as here)](https://github.com/openjdk/jdk/blob/db85090553ab14a84c3ed0a2604dd56c5b6e6982/src/java.desktop/share/classes/java/awt/Robot.java#L506C1-L507C43). Will changes to Robot.java be handled as separate PR + CSR ? We still use SecurityException in java.awt.Robot too. It is still needed for when the *desktop* denies access. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1866789983 From prr at openjdk.org Tue Dec 3 00:15:49 2024 From: prr at openjdk.org (Phil Race) Date: Tue, 3 Dec 2024 00:15:49 GMT Subject: Integrated: 8345143: Remove uses of SecurityManager in the java.desktop module In-Reply-To: References: Message-ID: On Thu, 28 Nov 2024 00:36:35 GMT, Phil Race wrote: > Remove SecurityManager related code in the desktop module that is not covered by other PRs This pull request has now been integrated. Changeset: 3f6c0424 Author: Phil Race URL: https://git.openjdk.org/jdk/commit/3f6c04247ff6ad69330bc219ed26944852954e85 Stats: 279 lines in 34 files changed: 1 ins; 246 del; 32 mod 8345143: Remove uses of SecurityManager in the java.desktop module Reviewed-by: azvegint, honkar ------------- PR: https://git.openjdk.org/jdk/pull/22424 From honkar at openjdk.org Tue Dec 3 00:26:53 2024 From: honkar at openjdk.org (Harshitha Onkar) Date: Tue, 3 Dec 2024 00:26:53 GMT Subject: RFR: 8345143: Remove uses of SecurityManager in the java.desktop module [v6] In-Reply-To: References: <8VPCW7QNB0ZRmg9Jf3icbbBcau6Kd0Xt02u76LibBWU=.c9d22099-2636-46c7-b363-a6af335e8bd2@github.com> Message-ID: On Tue, 3 Dec 2024 00:12:03 GMT, Phil Race wrote: >> test/jdk/lib/client/ExtendedRobot.java line 64: >> >>> 62: // syncDelay = AccessController.doPrivileged(new GetIntegerAction("java.awt.robotdelay", DEFAULT_SYNC_DELAY)); >>> 63: //} >>> 64: >> >> Not related to this PR changes but since ExtendedRobot was mentioned here, I went through Robot.java and it has few SecurityException in javadoc [(as here)](https://github.com/openjdk/jdk/blob/db85090553ab14a84c3ed0a2604dd56c5b6e6982/src/java.desktop/share/classes/java/awt/Robot.java#L506C1-L507C43). >> Will changes to Robot.java be handled as separate PR + CSR ? > >> Not related to this PR changes but since ExtendedRobot was mentioned here, I went through Robot.java and it has few SecurityException in javadoc [(as here)](https://github.com/openjdk/jdk/blob/db85090553ab14a84c3ed0a2604dd56c5b6e6982/src/java.desktop/share/classes/java/awt/Robot.java#L506C1-L507C43). Will changes to Robot.java be handled as separate PR + CSR ? > > We still use SecurityException in java.awt.Robot too. It is still needed for when the *desktop* denies access. Makes sense. Thanks for clarifying. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22424#discussion_r1866797014 From rriggs at openjdk.org Tue Dec 3 01:58:51 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 3 Dec 2024 01:58:51 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 22:51:55 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Merge branch 'master' into 8345325-sm-remove-getpropertyaction > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test > - 8345325: SM cleanup of GetPropertyAction in java.base > Remove use of GetPropertyAction > Remove sun/security/action/GetPropertyAction.java > - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. > Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp > methods to sun.security.util.SecurityProperties and rename them. > - Replace remaining calls to SecurityProperties.privilegedGetOverridable() > with SecurityProperties.getOverridableProperty() and remove > privilegedGetOverridable(). > - Merge > - Remove doPrivileged calls. > - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. > - Remove permission text from comments in Provider.java. > - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 CI Tiers 1-3 passed except for an unrelated communication failure. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22497#issuecomment-2513367581 From naoto at openjdk.org Tue Dec 3 02:11:41 2024 From: naoto at openjdk.org (Naoto Sato) Date: Tue, 3 Dec 2024 02:11:41 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 22:51:55 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Merge branch 'master' into 8345325-sm-remove-getpropertyaction > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test > - 8345325: SM cleanup of GetPropertyAction in java.base > Remove use of GetPropertyAction > Remove sun/security/action/GetPropertyAction.java > - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. > Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp > methods to sun.security.util.SecurityProperties and rename them. > - Replace remaining calls to SecurityProperties.privilegedGetOverridable() > with SecurityProperties.getOverridableProperty() and remove > privilegedGetOverridable(). > - Merge > - Remove doPrivileged calls. > - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. > - Remove permission text from comments in Provider.java. > - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 Marked as reviewed by naoto (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2474337606 From jlu at openjdk.org Tue Dec 3 02:29:16 2024 From: jlu at openjdk.org (Justin Lu) Date: Tue, 3 Dec 2024 02:29:16 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v5] In-Reply-To: References: Message-ID: > Please review this PR and corresponding CSR which includes a wide range of specification improvements for java.util.Locale. See the CSR for further detail. Other changes/suggestions are welcomed to be included as part of this change. > > APIDiff: https://cr.openjdk.org/~jlu/8341923_apidiff/java.base/java/util/Locale.html > Javadoc: https://cr.openjdk.org/~jlu/api/java.base/java/util/Locale.html Justin Lu has updated the pull request incrementally with one additional commit since the last revision: define 'locale-sensitive' as an index term ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22192/files - new: https://git.openjdk.org/jdk/pull/22192/files/871d635a..61196f60 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22192&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22192&range=03-04 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22192.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22192/head:pull/22192 PR: https://git.openjdk.org/jdk/pull/22192 From jlu at openjdk.org Tue Dec 3 02:29:16 2024 From: jlu at openjdk.org (Justin Lu) Date: Tue, 3 Dec 2024 02:29:16 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v4] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 23:00:20 GMT, Joe Darcy wrote: >> Justin Lu has updated the pull request incrementally with one additional commit since the last revision: >> >> reflect review > > src/java.base/share/classes/java/util/Locale.java line 76: > >> 74: * or cultural region. An API that requires a {@code Locale} to perform >> 75: * its task is locale-sensitive and uses the {@code Locale} >> 76: * to tailor information for the user. These locale-sensitive APIs > > Either as part of this change or in follow-up work, please consider defining a user-index term for "locale > -sensitive". That's a good idea. Added in https://github.com/openjdk/jdk/pull/22192/commits/61196f60d0722ad67cb0f1446e4fff520429b383. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22192#discussion_r1866930016 From liach at openjdk.org Tue Dec 3 04:16:41 2024 From: liach at openjdk.org (Chen Liang) Date: Tue, 3 Dec 2024 04:16:41 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v5] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 02:29:16 GMT, Justin Lu wrote: >> Please review this PR and corresponding CSR which includes a wide range of specification improvements for java.util.Locale. See the CSR for further detail. Other changes/suggestions are welcomed to be included as part of this change. >> >> APIDiff: https://cr.openjdk.org/~jlu/8341923_apidiff/java.base/java/util/Locale.html >> Javadoc: https://cr.openjdk.org/~jlu/api/java.base/java/util/Locale.html > > Justin Lu has updated the pull request incrementally with one additional commit since the last revision: > > define 'locale-sensitive' as an index term The new index looks good. I think the quote is usually used for cases where the indexed term has spaces, but it should be fine here. ------------- Marked as reviewed by liach (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22192#pullrequestreview-2474514003 From darcy at openjdk.org Tue Dec 3 04:22:41 2024 From: darcy at openjdk.org (Joe Darcy) Date: Tue, 3 Dec 2024 04:22:41 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v4] In-Reply-To: References: Message-ID: <8Qp7tZ4pmPRJhOPhh4aUKjjtnFE_jmRNLBa4cLkhEOs=.6b4fe0bc-774d-4409-b9af-e87e85a8354b@github.com> On Tue, 3 Dec 2024 02:26:03 GMT, Justin Lu wrote: >> src/java.base/share/classes/java/util/Locale.java line 76: >> >>> 74: * or cultural region. An API that requires a {@code Locale} to perform >>> 75: * its task is locale-sensitive and uses the {@code Locale} >>> 76: * to tailor information for the user. These locale-sensitive APIs >> >> Either as part of this change or in follow-up work, please consider defining a user-index term for "locale >> -sensitive". > > That's a good idea. Added in https://github.com/openjdk/jdk/pull/22192/commits/61196f60d0722ad67cb0f1446e4fff520429b383. Thanks. (No update to the CSR is needed for adding the index term.) ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22192#discussion_r1867012226 From alanb at openjdk.org Tue Dec 3 07:41:40 2024 From: alanb at openjdk.org (Alan Bateman) Date: Tue, 3 Dec 2024 07:41:40 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 22:51:55 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Merge branch 'master' into 8345325-sm-remove-getpropertyaction > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test > - 8345325: SM cleanup of GetPropertyAction in java.base > Remove use of GetPropertyAction > Remove sun/security/action/GetPropertyAction.java > - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. > Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp > methods to sun.security.util.SecurityProperties and rename them. > - Replace remaining calls to SecurityProperties.privilegedGetOverridable() > with SecurityProperties.getOverridableProperty() and remove > privilegedGetOverridable(). > - Merge > - Remove doPrivileged calls. > - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. > - Remove permission text from comments in Provider.java. > - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 Marked as reviewed by alanb (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2474803070 From eirbjo at openjdk.org Tue Dec 3 09:43:40 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Tue, 3 Dec 2024 09:43:40 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 22:51:55 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Merge branch 'master' into 8345325-sm-remove-getpropertyaction > - Remove unused import of Properties > - Update copyrights > Remove jdk/sun/security/action/Generify test > - 8345325: SM cleanup of GetPropertyAction in java.base > Remove use of GetPropertyAction > Remove sun/security/action/GetPropertyAction.java > - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. > Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp > methods to sun.security.util.SecurityProperties and rename them. > - Replace remaining calls to SecurityProperties.privilegedGetOverridable() > with SecurityProperties.getOverridableProperty() and remove > privilegedGetOverridable(). > - Merge > - Remove doPrivileged calls. > - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. > - Remove permission text from comments in Provider.java. > - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 src/java.base/share/classes/java/lang/StackStreamFactory.java line 87: > 85: * For Throwable to use StackWalker, set useNewThrowable to true. > 86: * Performance work and extensive testing is needed to replace the > 87: * VM built-in backtrace filled in Throwable with the StackWalker. This leftover comment used to belong to the `useNewThrowable` field which was removed in merge commit 4db74fef1e73c008d044c681d26c7444b2245316 back in 2017. You may consider removing it, since it now seems to belong to the `isDebug` field, which is not the case. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1867366019 From dmarkov at openjdk.org Tue Dec 3 11:07:37 2024 From: dmarkov at openjdk.org (Dmitry Markov) Date: Tue, 3 Dec 2024 11:07:37 GMT Subject: RFR: 8324491: Keyboard layout did not keep it state if it was changed when dialog is active In-Reply-To: References: Message-ID: On Wed, 27 Nov 2024 12:47:29 GMT, Dmitry Markov wrote: > If AWT/Swing app displays several windows and an user changes the keyboard layout and then closes the focused window, the app does not keep the keyboard layout changes. > > It is necessary to sync currentLocale and Windows keyboard layout values in `WInputMethod` class before component activation. Looking for volunteers to review the fix. Thanks in advance ------------- PR Comment: https://git.openjdk.org/jdk/pull/22411#issuecomment-2514235130 From rriggs at openjdk.org Tue Dec 3 14:45:22 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 3 Dec 2024 14:45:22 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v4] In-Reply-To: References: Message-ID: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 Roger Riggs has updated the pull request incrementally with one additional commit since the last revision: Remove an obsolete comment related to long ago removed useNewThrowable ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22497/files - new: https://git.openjdk.org/jdk/pull/22497/files/4c855033..6cb9b557 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=03 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22497&range=02-03 Stats: 5 lines in 1 file changed: 0 ins; 5 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/22497.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22497/head:pull/22497 PR: https://git.openjdk.org/jdk/pull/22497 From rriggs at openjdk.org Tue Dec 3 14:45:23 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 3 Dec 2024 14:45:23 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v3] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 09:40:39 GMT, Eirik Bj?rsn?s wrote: >> Roger Riggs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: >> >> - Merge branch 'master' into 8345325-sm-remove-getpropertyaction >> - Remove unused import of Properties >> - Update copyrights >> Remove jdk/sun/security/action/Generify test >> - 8345325: SM cleanup of GetPropertyAction in java.base >> Remove use of GetPropertyAction >> Remove sun/security/action/GetPropertyAction.java >> - Remove PutAllAction and GetBooleanAction classes as there are no more dependencies. >> Move GetPropertyAction.privilegedGetTimeoutProp and privilegedGetBooleanProp >> methods to sun.security.util.SecurityProperties and rename them. >> - Replace remaining calls to SecurityProperties.privilegedGetOverridable() >> with SecurityProperties.getOverridableProperty() and remove >> privilegedGetOverridable(). >> - Merge >> - Remove doPrivileged calls. >> - Remove dependency on SecurityConstants.ALL_PERMISSION from java.lang.Class. >> - Remove permission text from comments in Provider.java. >> - ... and 5 more: https://git.openjdk.org/jdk/compare/3a3bcd53...4c855033 > > src/java.base/share/classes/java/lang/StackStreamFactory.java line 87: > >> 85: * For Throwable to use StackWalker, set useNewThrowable to true. >> 86: * Performance work and extensive testing is needed to replace the >> 87: * VM built-in backtrace filled in Throwable with the StackWalker. > > This leftover comment used to belong to the `useNewThrowable` field which was removed in merge commit 4db74fef1e73c008d044c681d26c7444b2245316 back in 2017. > > You may consider removing it, since it now seems to belong to the `isDebug` field, which is not the case. No time like the present ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1867849183 From alanb at openjdk.org Tue Dec 3 14:48:43 2024 From: alanb at openjdk.org (Alan Bateman) Date: Tue, 3 Dec 2024 14:48:43 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v4] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 14:45:22 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request incrementally with one additional commit since the last revision: > > Remove an obsolete comment related to long ago removed useNewThrowable Marked as reviewed by alanb (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22497#pullrequestreview-2475918375 From eirbjo at openjdk.org Tue Dec 3 14:56:44 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Tue, 3 Dec 2024 14:56:44 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v4] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 14:45:22 GMT, Roger Riggs wrote: >> Remove sun/security/action/GetPropertyAction.java and all uses. >> >> Dependent on PR#22418 > > Roger Riggs has updated the pull request incrementally with one additional commit since the last revision: > > Remove an obsolete comment related to long ago removed useNewThrowable src/java.base/share/classes/java/lang/StackStreamFactory.java line 84: > 82: @Native private static final int FILL_LIVE_STACK_FRAMES = 0x100; > 83: > 84: static final boolean isDebug = This property should probably be compared with true in a case insensitive manner. It may be better to use `Boolean::getBoolean` instead. Justification: JDK-8155775 (commit e8cd76568da1b32b26491e80f498cff1409336b7) removed the `getProperty` method which was previously used to read this property: private static boolean getProperty(String key, boolean value) { String s = GetPropertyAction.getProperty(key); if (s != null) { return Boolean.parseBoolean(s); } return value; } `isDebug` was initialized with a false default if the system property was null: final static boolean isDebug = getProperty("stackwalk.debug", false); ``` I doubt the change in case handling was intentional, @cl4es may confirm. Based on the above, I think we should consider using Boolean.getBoolean here, as that is case-insensitive and returns false for null: Suggestion: static final boolean isDebug = Boolean.getBoolean("stackwalk.debug"); ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1867880288 From rriggs at openjdk.org Tue Dec 3 14:59:44 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 3 Dec 2024 14:59:44 GMT Subject: RFR: 8345325: SM cleanup of GetPropertyAction in java.base [v4] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 14:53:41 GMT, Eirik Bj?rsn?s wrote: >> Roger Riggs has updated the pull request incrementally with one additional commit since the last revision: >> >> Remove an obsolete comment related to long ago removed useNewThrowable > > src/java.base/share/classes/java/lang/StackStreamFactory.java line 84: > >> 82: @Native private static final int FILL_LIVE_STACK_FRAMES = 0x100; >> 83: >> 84: static final boolean isDebug = > > This property should probably be compared with true in a case insensitive manner. It may be better to use `Boolean::getBoolean` instead. > > Justification: > > JDK-8155775 (commit e8cd76568da1b32b26491e80f498cff1409336b7) removed the `getProperty` method which was previously used to read this property: > > > private static boolean getProperty(String key, boolean value) { > String s = GetPropertyAction.getProperty(key); > if (s != null) { > return Boolean.parseBoolean(s); > } > return value; > } > > > `isDebug` was initialized with a false default if the system property was null: > > > final static boolean isDebug = getProperty("stackwalk.debug", false); > ``` > > I doubt the change in case handling was intentional, @cl4es may confirm. > > Based on the above, I think we should consider using Boolean.getBoolean here, as that is case-insensitive and returns false for null: > > Suggestion: > > static final boolean isDebug = Boolean.getBoolean("stackwalk.debug"); Changing the behavior is out of scope for this pr. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22497#discussion_r1867886415 From rriggs at openjdk.org Tue Dec 3 15:02:46 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 3 Dec 2024 15:02:46 GMT Subject: Integrated: 8345325: SM cleanup of GetPropertyAction in java.base In-Reply-To: References: Message-ID: On Mon, 2 Dec 2024 20:12:39 GMT, Roger Riggs wrote: > Remove sun/security/action/GetPropertyAction.java and all uses. > > Dependent on PR#22418 This pull request has now been integrated. Changeset: fcf185c8 Author: Roger Riggs URL: https://git.openjdk.org/jdk/commit/fcf185c8b425a6984eb145c3127f97e811d345d7 Stats: 241 lines in 11 files changed: 0 ins; 228 del; 13 mod 8345325: SM cleanup of GetPropertyAction in java.base Reviewed-by: alanb, lancea, naoto, mchung ------------- PR: https://git.openjdk.org/jdk/pull/22497 From aivanov at openjdk.org Tue Dec 3 16:42:43 2024 From: aivanov at openjdk.org (Alexey Ivanov) Date: Tue, 3 Dec 2024 16:42:43 GMT Subject: RFR: 8324491: Keyboard layout did not keep it state if it was changed when dialog is active In-Reply-To: References: Message-ID: <2rsx0fDpxzi9J3eL3VdbWsH3ScmmwRErdR3Hc_Bl-tg=.f0f9267e-be86-409e-abc6-6e8e19a6011c@github.com> On Wed, 27 Nov 2024 12:47:29 GMT, Dmitry Markov wrote: > If AWT/Swing app displays several windows and an user changes the keyboard layout and then closes the focused window, the app does not keep the keyboard layout changes. > > It is necessary to sync currentLocale and Windows keyboard layout values in `WInputMethod` class before component activation. Looks good to me. The keyboard layout is preserved after closing the dialog. I used SwingSet2 and **Show Input Dialog** to test the changes. ------------- Marked as reviewed by aivanov (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22411#pullrequestreview-2476237306 From jlu at openjdk.org Tue Dec 3 17:18:48 2024 From: jlu at openjdk.org (Justin Lu) Date: Tue, 3 Dec 2024 17:18:48 GMT Subject: RFR: 8344589: Update IANA Language Subtag Registry to Version 2024-11-19 In-Reply-To: References: Message-ID: On Wed, 20 Nov 2024 02:59:54 GMT, Justin Lu wrote: > Please review this PR which keeps the IANA language subtag registry data up to date with release _2024-11-19_. > > The changes are trivial and Locale tests pass as expected. Thanks for the reviews. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22265#issuecomment-2515142741 From jlu at openjdk.org Tue Dec 3 17:18:49 2024 From: jlu at openjdk.org (Justin Lu) Date: Tue, 3 Dec 2024 17:18:49 GMT Subject: Integrated: 8344589: Update IANA Language Subtag Registry to Version 2024-11-19 In-Reply-To: References: Message-ID: On Wed, 20 Nov 2024 02:59:54 GMT, Justin Lu wrote: > Please review this PR which keeps the IANA language subtag registry data up to date with release _2024-11-19_. > > The changes are trivial and Locale tests pass as expected. This pull request has now been integrated. Changeset: 9267dfa6 Author: Justin Lu URL: https://git.openjdk.org/jdk/commit/9267dfa63b1d6b3f339782d2b720055a3da8ae6a Stats: 13 lines in 2 files changed: 10 ins; 0 del; 3 mod 8344589: Update IANA Language Subtag Registry to Version 2024-11-19 Reviewed-by: iris, lancea, naoto ------------- PR: https://git.openjdk.org/jdk/pull/22265 From azvegint at openjdk.org Tue Dec 3 18:16:43 2024 From: azvegint at openjdk.org (Alexander Zvegintsev) Date: Tue, 3 Dec 2024 18:16:43 GMT Subject: RFR: 8324491: Keyboard layout did not keep it state if it was changed when dialog is active In-Reply-To: References: Message-ID: <4_Jp5Iwmz3L2g7G2HJBqj1O_0Tqk2FrxH1qfqymcjTQ=.5d250b48-689d-4a16-80db-e6b289676655@github.com> On Wed, 27 Nov 2024 12:47:29 GMT, Dmitry Markov wrote: > If AWT/Swing app displays several windows and an user changes the keyboard layout and then closes the focused window, the app does not keep the keyboard layout changes. > > It is necessary to sync currentLocale and Windows keyboard layout values in `WInputMethod` class before component activation. Marked as reviewed by azvegint (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22411#pullrequestreview-2476468276 From dmarkov at openjdk.org Tue Dec 3 18:40:45 2024 From: dmarkov at openjdk.org (Dmitry Markov) Date: Tue, 3 Dec 2024 18:40:45 GMT Subject: Integrated: 8324491: Keyboard layout didn't keep its state if it was changed when dialog was active In-Reply-To: References: Message-ID: On Wed, 27 Nov 2024 12:47:29 GMT, Dmitry Markov wrote: > If AWT/Swing app displays several windows and an user changes the keyboard layout and then closes the focused window, the app does not keep the keyboard layout changes. > > It is necessary to sync currentLocale and Windows keyboard layout values in `WInputMethod` class before component activation. This pull request has now been integrated. Changeset: 2be07b5f Author: Dmitry Markov URL: https://git.openjdk.org/jdk/commit/2be07b5f9d2f3f0b885feb08ff10a57824ea5748 Stats: 5 lines in 1 file changed: 4 ins; 0 del; 1 mod 8324491: Keyboard layout didn't keep its state if it was changed when dialog was active Reviewed-by: aivanov, azvegint ------------- PR: https://git.openjdk.org/jdk/pull/22411 From jlu at openjdk.org Wed Dec 4 20:59:48 2024 From: jlu at openjdk.org (Justin Lu) Date: Wed, 4 Dec 2024 20:59:48 GMT Subject: RFR: 8341923: java.util.Locale class specification improvements [v5] In-Reply-To: References: Message-ID: On Tue, 3 Dec 2024 02:29:16 GMT, Justin Lu wrote: >> Please review this PR and corresponding CSR which includes a wide range of specification improvements for java.util.Locale. See the CSR for further detail. Other changes/suggestions are welcomed to be included as part of this change. >> >> APIDiff: https://cr.openjdk.org/~jlu/8341923_apidiff/java.base/java/util/Locale.html >> Javadoc: https://cr.openjdk.org/~jlu/api/java.base/java/util/Locale.html > > Justin Lu has updated the pull request incrementally with one additional commit since the last revision: > > define 'locale-sensitive' as an index term Thanks for the reviews! ------------- PR Comment: https://git.openjdk.org/jdk/pull/22192#issuecomment-2518543992 From jlu at openjdk.org Wed Dec 4 20:59:48 2024 From: jlu at openjdk.org (Justin Lu) Date: Wed, 4 Dec 2024 20:59:48 GMT Subject: Integrated: 8341923: java.util.Locale class specification improvements In-Reply-To: References: Message-ID: <9BvcEfvTGwcnaohpiFamMaWroZHD5dPjAG_zIX2C_bM=.103b92aa-0ab8-431f-9091-10c4d765d309@github.com> On Mon, 18 Nov 2024 07:41:31 GMT, Justin Lu wrote: > Please review this PR and corresponding CSR which includes a wide range of specification improvements for java.util.Locale. See the CSR for further detail. Other changes/suggestions are welcomed to be included as part of this change. > > APIDiff: https://cr.openjdk.org/~jlu/8341923_apidiff/java.base/java/util/Locale.html > Javadoc: https://cr.openjdk.org/~jlu/api/java.base/java/util/Locale.html This pull request has now been integrated. Changeset: ee0f88c9 Author: Justin Lu URL: https://git.openjdk.org/jdk/commit/ee0f88c90155c26302425e33d3137c064e70ba6e Stats: 327 lines in 1 file changed: 105 ins; 89 del; 133 mod 8341923: java.util.Locale class specification improvements Reviewed-by: liach, naoto ------------- PR: https://git.openjdk.org/jdk/pull/22192 From liach at openjdk.org Thu Dec 5 20:44:59 2024 From: liach at openjdk.org (Chen Liang) Date: Thu, 5 Dec 2024 20:44:59 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: > Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. > > To reviewers, there are some redundant changes and notes: > > - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. > - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: > - `BoundAttribute::payloadLen` for javac attribute tests > - Annotation reading/writing for javac annotation tests > - Line number changes to: > - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java > - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java > - Move from legacy jdk.internal.classfile to java.lang.classfile in: > - test/langtools/tools/javac/NoStringToLower.java and > - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java > - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java > > - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. > > Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 ------------- Changes: https://git.openjdk.org/jdk/pull/22420/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22420&range=01 Stats: 634 lines in 360 files changed: 2 ins; 555 del; 77 mod Patch: https://git.openjdk.org/jdk/pull/22420.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22420/head:pull/22420 PR: https://git.openjdk.org/jdk/pull/22420 From mchung at openjdk.org Thu Dec 5 22:02:40 2024 From: mchung at openjdk.org (Mandy Chung) Date: Thu, 5 Dec 2024 22:02:40 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Thu, 5 Dec 2024 20:44:59 GMT, Chen Liang wrote: >> Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. >> >> To reviewers, there are some redundant changes and notes: >> >> - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. >> - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: >> - `BoundAttribute::payloadLen` for javac attribute tests >> - Annotation reading/writing for javac annotation tests >> - Line number changes to: >> - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java >> - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java >> - Move from legacy jdk.internal.classfile to java.lang.classfile in: >> - test/langtools/tools/javac/NoStringToLower.java and >> - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java >> - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >> >> - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. >> >> Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. > > Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview > - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 The change looks okay to me except `ParameterAnnotations.java`. This task is part of JEP 484 and test-only. It seems good to backport to 24. test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java line 643: > 641: > 642: Task.Result result = new JavacTask(tb) > 643: .processors(new TestAP()) I assume this fix does not require this change, right? If so, better to keep the original code and do this cleanup as a separate issue. ------------- PR Review: https://git.openjdk.org/jdk/pull/22420#pullrequestreview-2483057967 PR Review Comment: https://git.openjdk.org/jdk/pull/22420#discussion_r1872207964 From liach at openjdk.org Thu Dec 5 22:29:40 2024 From: liach at openjdk.org (Chen Liang) Date: Thu, 5 Dec 2024 22:29:40 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: <0UU_yVYVqg3FQpCHy7i7hQYidoMigQtXKbTJdNIUMbQ=.d46b4331-cd85-4199-bac3-9b48454e9add@github.com> On Thu, 5 Dec 2024 21:54:19 GMT, Mandy Chung wrote: >> Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: >> >> - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview >> - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 > > test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java line 643: > >> 641: >> 642: Task.Result result = new JavacTask(tb) >> 643: .processors(new TestAP()) > > I assume this fix does not require this change, right? If so, better to keep the original code and do this cleanup as a separate issue. It is required. If we use the command line and FQN to specify a processor like in the current code without preview, this test fails with some classpath error. > Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. I should attach the exact error message: test: testInnerClass [DIRECT]: - compiler.err.proc.processor.not.found: ParameterAnnotations$TestAP - compiler.err.proc.no.explicit.annotation.processing.requested: T$I 2 errors Exception running test testInnerClass: toolbox.Task$TaskError: Task javac failed: rc=1 toolbox.Task$TaskError: Task javac failed: rc=1 at toolbox.AbstractTask.checkExit(AbstractTask.java:154) at toolbox.JavacTask.run(JavacTask.java:381) at toolbox.AbstractTask.run(AbstractTask.java:102) at toolbox.JavacTask.run(JavacTask.java:52) at toolbox.JavacTask.run(JavacTask.java:321) at ParameterAnnotations.doTest(ParameterAnnotations.java:650) at ParameterAnnotations.testInnerClass(ParameterAnnotations.java:151) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) at java.base/java.lang.reflect.Method.invoke(Method.java:565) at toolbox.TestRunner.runTests(TestRunner.java:91) at ParameterAnnotations.runTests(ParameterAnnotations.java:82) at ParameterAnnotations.main(ParameterAnnotations.java:73) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) at java.base/java.lang.reflect.Method.invoke(Method.java:565) at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333) at java.base/java.lang.Thread.run(Thread.java:1447) Same for all 5 tests in this file. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22420#discussion_r1872240998 From liach at openjdk.org Thu Dec 5 22:39:38 2024 From: liach at openjdk.org (Chen Liang) Date: Thu, 5 Dec 2024 22:39:38 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: <0UU_yVYVqg3FQpCHy7i7hQYidoMigQtXKbTJdNIUMbQ=.d46b4331-cd85-4199-bac3-9b48454e9add@github.com> References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> <0UU_yVYVqg3FQpCHy7i7hQYidoMigQtXKbTJdNIUMbQ=.d46b4331-cd85-4199-bac3-9b48454e9add@github.com> Message-ID: On Thu, 5 Dec 2024 22:26:31 GMT, Chen Liang wrote: >> test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java line 643: >> >>> 641: >>> 642: Task.Result result = new JavacTask(tb) >>> 643: .processors(new TestAP()) >> >> I assume this fix does not require this change, right? If so, better to keep the original code and do this cleanup as a separate issue. > > It is required. If we use the command line and FQN to specify a processor like in the current code without preview, this test fails with some classpath error. > >> Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java > >>Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. > > I should attach the exact error message: > > > test: testInnerClass > [DIRECT]: > - compiler.err.proc.processor.not.found: ParameterAnnotations$TestAP > - compiler.err.proc.no.explicit.annotation.processing.requested: T$I > 2 errors > Exception running test testInnerClass: toolbox.Task$TaskError: Task javac failed: rc=1 > toolbox.Task$TaskError: Task javac failed: rc=1 > at toolbox.AbstractTask.checkExit(AbstractTask.java:154) > at toolbox.JavacTask.run(JavacTask.java:381) > at toolbox.AbstractTask.run(AbstractTask.java:102) > at toolbox.JavacTask.run(JavacTask.java:52) > at toolbox.JavacTask.run(JavacTask.java:321) > at ParameterAnnotations.doTest(ParameterAnnotations.java:650) > at ParameterAnnotations.testInnerClass(ParameterAnnotations.java:151) > at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) > at java.base/java.lang.reflect.Method.invoke(Method.java:565) > at toolbox.TestRunner.runTests(TestRunner.java:91) > at ParameterAnnotations.runTests(ParameterAnnotations.java:82) > at ParameterAnnotations.main(ParameterAnnotations.java:73) > at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104) > at java.base/java.lang.reflect.Method.invoke(Method.java:565) > at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333) > at java.base/java.lang.Thread.run(Thread.java:1447) > > > Same for all 5 tests in this file. Filed https://bugs.openjdk.org/browse/JDK-8345622. There is no similar issues that happen as a conjunction of preview and annotation processing. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22420#discussion_r1872252558 From mchung at openjdk.org Thu Dec 5 23:04:40 2024 From: mchung at openjdk.org (Mandy Chung) Date: Thu, 5 Dec 2024 23:04:40 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Thu, 5 Dec 2024 20:44:59 GMT, Chen Liang wrote: >> Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. >> >> To reviewers, there are some redundant changes and notes: >> >> - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. >> - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: >> - `BoundAttribute::payloadLen` for javac attribute tests >> - Annotation reading/writing for javac annotation tests >> - Line number changes to: >> - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java >> - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java >> - Move from legacy jdk.internal.classfile to java.lang.classfile in: >> - test/langtools/tools/javac/NoStringToLower.java and >> - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java >> - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >> >> - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. >> >> Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. > > Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview > - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 Thanks for filing the issue to follow up. ------------- Marked as reviewed by mchung (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22420#pullrequestreview-2483183112 From asotona at openjdk.org Fri Dec 6 07:01:45 2024 From: asotona at openjdk.org (Adam Sotona) Date: Fri, 6 Dec 2024 07:01:45 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Thu, 5 Dec 2024 20:44:59 GMT, Chen Liang wrote: >> Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. >> >> To reviewers, there are some redundant changes and notes: >> >> - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. >> - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: >> - `BoundAttribute::payloadLen` for javac attribute tests >> - Annotation reading/writing for javac annotation tests >> - Line number changes to: >> - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java >> - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java >> - Move from legacy jdk.internal.classfile to java.lang.classfile in: >> - test/langtools/tools/javac/NoStringToLower.java and >> - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java >> - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >> >> - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. >> >> Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. > > Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview > - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 Looks good to me, thanks. ------------- Marked as reviewed by asotona (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22420#pullrequestreview-2483795644 From liach at openjdk.org Fri Dec 6 14:27:45 2024 From: liach at openjdk.org (Chen Liang) Date: Fri, 6 Dec 2024 14:27:45 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Thu, 5 Dec 2024 20:44:59 GMT, Chen Liang wrote: >> Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. >> >> To reviewers, there are some redundant changes and notes: >> >> - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. >> - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: >> - `BoundAttribute::payloadLen` for javac attribute tests >> - Annotation reading/writing for javac annotation tests >> - Line number changes to: >> - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java >> - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java >> - Move from legacy jdk.internal.classfile to java.lang.classfile in: >> - test/langtools/tools/javac/NoStringToLower.java and >> - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java >> - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >> >> - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. >> >> Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. > > Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview > - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 Thanks for the reviews! ------------- PR Comment: https://git.openjdk.org/jdk/pull/22420#issuecomment-2523362333 From liach at openjdk.org Fri Dec 6 14:27:46 2024 From: liach at openjdk.org (Chen Liang) Date: Fri, 6 Dec 2024 14:27:46 GMT Subject: Integrated: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 In-Reply-To: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Wed, 27 Nov 2024 23:10:15 GMT, Chen Liang wrote: > Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. > > To reviewers, there are some redundant changes and notes: > > - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. > - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: > - `BoundAttribute::payloadLen` for javac attribute tests > - Annotation reading/writing for javac annotation tests > - Line number changes to: > - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java > - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java > - Move from legacy jdk.internal.classfile to java.lang.classfile in: > - test/langtools/tools/javac/NoStringToLower.java and > - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java > - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java > > - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. > > Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. This pull request has now been integrated. Changeset: 49664195 Author: Chen Liang URL: https://git.openjdk.org/jdk/commit/496641955041c5e48359e6256a4a61812653d900 Stats: 634 lines in 360 files changed: 2 ins; 555 del; 77 mod 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 Reviewed-by: mchung, asotona ------------- PR: https://git.openjdk.org/jdk/pull/22420 From liach at openjdk.org Fri Dec 6 15:08:47 2024 From: liach at openjdk.org (Chen Liang) Date: Fri, 6 Dec 2024 15:08:47 GMT Subject: RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 [v2] In-Reply-To: References: <3FonQjV3pn1bynQC4dT-Mo2ttwRkmxuAkY0y9TbB0u8=.5ea6d9ce-068b-4d1d-81e1-548f59761641@github.com> Message-ID: On Thu, 5 Dec 2024 20:44:59 GMT, Chen Liang wrote: >> Remove the redundant `@enablePreview` and `--enable-preview` flags for enabling ClassFile API in the tests. The remainder of these flags in all tests seem to serve preview APIs (such as ScopedValue) or language features (primitive pattern, module imports, etc.), or testing the enable preview flag itself. Now there is fewer than 100 `@enablePreview` in the `test` directory. >> >> To reviewers, there are some redundant changes and notes: >> >> - There's one security test that used `ModuleInfoWriter` that depends on ClassFile API. >> - Removed unnecessary exports of `jdk.internal.classfile.impl`. Remaining uses are: >> - `BoundAttribute::payloadLen` for javac attribute tests >> - Annotation reading/writing for javac annotation tests >> - Line number changes to: >> - test/langtools/tools/javac/linenumbers/NestedLineNumberTest.java >> - test/langtools/tools/javac/linenumbers/NullCheckLineNumberTest.java >> - Move from legacy jdk.internal.classfile to java.lang.classfile in: >> - test/langtools/tools/javac/NoStringToLower.java and >> - test/langtools/tools/javac/T8003967/DetectMutableStaticFields.java >> - Weird annotation processor behavior in test/langtools/tools/javac/annotations/parameter/ParameterAnnotations.java >> >> - Without preview and using explicit file name, the javac task fails; using the builder live AP object works both with and without preview. >> >> Testing: tier 1-5. Please inform me if any of these tests belong to higher tiers. > > Chen Liang has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains two commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into cleanup/cf-preview > - 8334733: Remove obsolete @enablePreview from tests after JDK-83324714 >From internal discussion, this task is logically associated with the finalization of ClassFile API and is best done for the same release 24. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22420#issuecomment-2523450991 From liach at openjdk.org Fri Dec 6 15:17:26 2024 From: liach at openjdk.org (Chen Liang) Date: Fri, 6 Dec 2024 15:17:26 GMT Subject: [jdk24] RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 Message-ID: Hi all, This pull request contains a backport of commit [49664195](https://github.com/openjdk/jdk/commit/496641955041c5e48359e6256a4a61812653d900) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository. This is a test-only change so it is eligible for backport; in addition, this change is logically part of the Class-File API finalized in JDK 24. The commit being backported was authored by Chen Liang on 6 Dec 2024 and was reviewed by Mandy Chung and Adam Sotona. Thanks! ------------- Commit messages: - Backport 496641955041c5e48359e6256a4a61812653d900 Changes: https://git.openjdk.org/jdk/pull/22607/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22607&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8334733 Stats: 634 lines in 360 files changed: 2 ins; 555 del; 77 mod Patch: https://git.openjdk.org/jdk/pull/22607.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22607/head:pull/22607 PR: https://git.openjdk.org/jdk/pull/22607 From duke at openjdk.org Fri Dec 6 21:40:55 2024 From: duke at openjdk.org (duke) Date: Fri, 6 Dec 2024 21:40:55 GMT Subject: Withdrawn: 8195686: ISO-8859-8-i charset cannot be decoded, should be mapped to ISO-8859-8 In-Reply-To: References: Message-ID: On Fri, 23 Aug 2024 10:38:38 GMT, Pratiksha.Sawant wrote: > Mapping ISO-8859-8-I charset to ISO-8859-8. > Below mentioned 2 aliases are added as part of this:- > **ISO-8859-8-I** > **ISO8859-8-I** > > The bug report for the same:- https://bugs.openjdk.org/browse/JDK-8195686 This pull request has been closed without being integrated. ------------- PR: https://git.openjdk.org/jdk/pull/20690 From eirbjo at openjdk.org Sat Dec 7 19:48:49 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Sat, 7 Dec 2024 19:48:49 GMT Subject: RFR: 8344252: SM cleanup in java.util classes [v3] In-Reply-To: <4MWPGqjfxblaSlsMPqS9V49dZxHfUckyAdopHxdpXFc=.3ba4f181-e96f-4228-afc9-ec2221a2fc45@github.com> References: <4MWPGqjfxblaSlsMPqS9V49dZxHfUckyAdopHxdpXFc=.3ba4f181-e96f-4228-afc9-ec2221a2fc45@github.com> Message-ID: <29G6N7CbeIyNfvUMTOYWf4g1WVPTN1JhvDdj_mZ614I=.f85cdf01-22f9-4a60-aa18-eb7d7fb4c2dc@github.com> On Fri, 15 Nov 2024 17:52:28 GMT, Roger Riggs wrote: >> Remove use of doPrivileged and SecurityManager in java.util. > > Roger Riggs has updated the pull request incrementally with one additional commit since the last revision: > > Correct @see link syntax in AbstractResourceBundleProvider src/java.base/share/classes/java/util/ResourceBundle.java line 3657: > 3655: } > 3656: > 3657: private static final boolean TRACE_ON = Boolean.getBoolean( This update seems to have broken the tracing feature of ResourceBundle. The previous code called `GetPropertyAction::privilegedGetProperty` to get the system property "resource.bundle.debug" with a default of "false". It then used `Boolean::parseBoolean` to compare it to "true", ignoring case. The new code uses `System::getProperty` to get the same property, then calls `Boolean::getBoolean` which calls `System::getProperty` to get the value of the property which name is either "false" or the result of looking up "resource.bundle.debug" >From what I can tell, it is now not possible to enable tracing. Seems like we could simply use `Boolean.getBoolean("resource.bundle.debug")` instead? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22122#discussion_r1874554294 From alanb at openjdk.org Mon Dec 9 08:01:45 2024 From: alanb at openjdk.org (Alan Bateman) Date: Mon, 9 Dec 2024 08:01:45 GMT Subject: RFR: 8344252: SM cleanup in java.util classes [v3] In-Reply-To: <29G6N7CbeIyNfvUMTOYWf4g1WVPTN1JhvDdj_mZ614I=.f85cdf01-22f9-4a60-aa18-eb7d7fb4c2dc@github.com> References: <4MWPGqjfxblaSlsMPqS9V49dZxHfUckyAdopHxdpXFc=.3ba4f181-e96f-4228-afc9-ec2221a2fc45@github.com> <29G6N7CbeIyNfvUMTOYWf4g1WVPTN1JhvDdj_mZ614I=.f85cdf01-22f9-4a60-aa18-eb7d7fb4c2dc@github.com> Message-ID: On Sat, 7 Dec 2024 19:44:05 GMT, Eirik Bj?rsn?s wrote: > Seems like we could simply use `Boolean.getBoolean("resource.bundle.debug")` instead? Naoto may know the history on this property. It may have been introduced for debugging when working on the RB implementation or maybe it was introduced to allow developers to debug, not sure. If the latter then it's important to preserve long standing behavior. If the former, and it was never documented, there is a lot more flexibility to change. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22122#discussion_r1875526278 From eirbjo at openjdk.org Mon Dec 9 09:02:47 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Mon, 9 Dec 2024 09:02:47 GMT Subject: RFR: 8344252: SM cleanup in java.util classes [v3] In-Reply-To: References: <4MWPGqjfxblaSlsMPqS9V49dZxHfUckyAdopHxdpXFc=.3ba4f181-e96f-4228-afc9-ec2221a2fc45@github.com> <29G6N7CbeIyNfvUMTOYWf4g1WVPTN1JhvDdj_mZ614I=.f85cdf01-22f9-4a60-aa18-eb7d7fb4c2dc@github.com> Message-ID: On Mon, 9 Dec 2024 07:58:35 GMT, Alan Bateman wrote: > If the former, and it was never documented, there is a lot more flexibility to change. Fair enough. However, this SM change seems to accidentally have introduced a bug where the system property is read twice, first calling System.getProperty to look up the name of the system property which is then looked up by Boolean.getBoolean. That behavior just seems broken. @RogerRiggs may have intended to use `Boolean::parseBoolean` instead: `Boolean.parseBoolean(System.getProperty("resource.bundle.debug", "false"))` which is equivalent to: `Boolean.getBoolean("resource.bundle.debug")` ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22122#discussion_r1875603019 From ihse at openjdk.org Mon Dec 9 12:22:25 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 12:22:25 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed Message-ID: Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. I have located these modified files using: git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list and then run a script to update the copyright year to 2024 on these files. I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. ------------- Commit messages: - 8345797: Update copyright year to 2024 for client-libs in files where it was missed Changes: https://git.openjdk.org/jdk/pull/22638/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22638&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345797 Stats: 326 lines in 344 files changed: 0 ins; 0 del; 326 mod Patch: https://git.openjdk.org/jdk/pull/22638.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22638/head:pull/22638 PR: https://git.openjdk.org/jdk/pull/22638 From ihse at openjdk.org Mon Dec 9 12:34:53 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 12:34:53 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed Message-ID: Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. I have located these modified files using: git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list and then run a script to update the copyright year to 2024 on these files. I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. ------------- Commit messages: - 8345799: Update copyright year to 2024 for core-libs in files where it was missed Changes: https://git.openjdk.org/jdk/pull/22640/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22640&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345799 Stats: 432 lines in 436 files changed: 0 ins; 0 del; 432 mod Patch: https://git.openjdk.org/jdk/pull/22640.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22640/head:pull/22640 PR: https://git.openjdk.org/jdk/pull/22640 From ihse at openjdk.org Mon Dec 9 12:37:37 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 12:37:37 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: Add more client files ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22638/files - new: https://git.openjdk.org/jdk/pull/22638/files/49387718..e196d3f6 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22638&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22638&range=00-01 Stats: 16 lines in 17 files changed: 0 ins; 0 del; 16 mod Patch: https://git.openjdk.org/jdk/pull/22638.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22638/head:pull/22638 PR: https://git.openjdk.org/jdk/pull/22638 From ihse at openjdk.org Mon Dec 9 13:03:06 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 13:03:06 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: Add more core-libs files ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22640/files - new: https://git.openjdk.org/jdk/pull/22640/files/e7cfe0f7..8e040c3a Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22640&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22640&range=00-01 Stats: 9 lines in 9 files changed: 0 ins; 0 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/22640.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22640/head:pull/22640 PR: https://git.openjdk.org/jdk/pull/22640 From dfuchs at openjdk.org Mon Dec 9 13:30:43 2024 From: dfuchs at openjdk.org (Daniel Fuchs) Date: Mon, 9 Dec 2024 13:30:43 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 13:03:06 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Add more core-libs files changes to sun.net and java.naming/jdk.naming.* look ok ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2527957595 From kevinw at openjdk.org Mon Dec 9 14:02:39 2024 From: kevinw at openjdk.org (Kevin Walls) Date: Mon, 9 Dec 2024 14:02:39 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 13:03:06 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Add more core-libs files Looks good. They all seem to follow the pattern, I looked at some and yes they have changes in 2024 but no year update. One of them was mine I noticed! ------------- Marked as reviewed by kevinw (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2488883450 From rriggs at openjdk.org Mon Dec 9 15:19:38 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 9 Dec 2024 15:19:38 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 13:03:06 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Add more core-libs files Copyright dates in third party files are not updated uniformly. See the previous comment. That git query isn't correct for all the files in the repo. In particular, the copyrights on third party files are NOT updated uniformly when new versions are applied. In particular, XML files are NOT updated. ------------- Changes requested by rriggs (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2489132284 PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2528303669 From kevinw at openjdk.org Mon Dec 9 15:28:38 2024 From: kevinw at openjdk.org (Kevin Walls) Date: Mon, 9 Dec 2024 15:28:38 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 13:03:06 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Add more core-libs files I also meant to note that there are updates to binaries, src/java.base/share/classes/jdk/internal/icu/impl/data/icudt76b/... which maybe isn't intentional, or I just don't understand? ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2528357715 From ihse at openjdk.org Mon Dec 9 15:42:57 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 15:42:57 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:26:00 GMT, Kevin Walls wrote: > I also meant to note that there are updates to binaries, src/java.base/share/classes/jdk/internal/icu/impl/data/icudt76b/... which maybe isn't intentional, or I just don't understand? That was certainly not intentional! I'm not sure how that happened, I need to look at my copyright update script again... ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2528425161 From ihse at openjdk.org Mon Dec 9 15:42:57 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 15:42:57 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: Revert changes to binary files ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22640/files - new: https://git.openjdk.org/jdk/pull/22640/files/8e040c3a..c8d541f9 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22640&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22640&range=01-02 Stats: 0 lines in 4 files changed: 0 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/22640.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22640/head:pull/22640 PR: https://git.openjdk.org/jdk/pull/22640 From ihse at openjdk.org Mon Dec 9 15:48:38 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 15:48:38 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:16:10 GMT, Roger Riggs wrote: > That git query isn't correct for all the files in the repo. In particular, the copyrights on third party files are NOT updated uniformly when new versions are applied. In particular, XML files are NOT updated. I'm not sure I understand what you mean. Are you saying that I did not update files that should have been updated, or that I updated files that should not have been updated? The only 3rd party XML files I know about are the ones in `make/data/cldr`. They have certainly been updated in 2024 from upstream, but they do not carry an Oracle copyright header, so there is nothing there to update. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2528451279 From rriggs at openjdk.org Mon Dec 9 16:06:46 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 9 Dec 2024 16:06:46 GMT Subject: RFR: 8344252: SM cleanup in java.util classes [v3] In-Reply-To: References: <4MWPGqjfxblaSlsMPqS9V49dZxHfUckyAdopHxdpXFc=.3ba4f181-e96f-4228-afc9-ec2221a2fc45@github.com> <29G6N7CbeIyNfvUMTOYWf4g1WVPTN1JhvDdj_mZ614I=.f85cdf01-22f9-4a60-aa18-eb7d7fb4c2dc@github.com> Message-ID: <2kTf09uckfME3hGDnGELXhdx4B5Gj5OvnfyDpqT0fG0=.80cd52a7-f2c8-46db-aae8-8cce74f9bcf0@github.com> On Mon, 9 Dec 2024 08:58:19 GMT, Eirik Bj?rsn?s wrote: >>> Seems like we could simply use `Boolean.getBoolean("resource.bundle.debug")` instead? >> >> Naoto may know the history on this property. It may have been introduced for debugging when working on the RB implementation or maybe it was introduced to allow developers to debug, not sure. If the latter then it's important to preserve long standing behavior. If the former, and it was never documented, there is a lot more flexibility to change. > >> If the former, and it was never documented, there is a lot more flexibility to change. > > Fair enough. However, this SM change seems to accidentally have introduced a bug where the system property is read twice, first calling System.getProperty to look up the name of the system property which is then looked up by Boolean.getBoolean. That behavior just seems broken. > > @RogerRiggs may have intended to use `Boolean::parseBoolean` instead: > > `Boolean.parseBoolean(System.getProperty("resource.bundle.debug", "false"))` > > which is equivalent to: > > `Boolean.getBoolean("resource.bundle.debug")` Filed https://bugs.openjdk.org/browse/JDK-8345818. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22122#discussion_r1876255089 From rriggs at openjdk.org Mon Dec 9 17:26:49 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 9 Dec 2024 17:26:49 GMT Subject: RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle debug Message-ID: Replace broken getProperty with Boolean.getBoolean. Manual testing confirms trace messages are enabled with `-Dresource.bundle.debug=true` ------------- Commit messages: - 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug Changes: https://git.openjdk.org/jdk/pull/22649/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22649&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345818 Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22649.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22649/head:pull/22649 PR: https://git.openjdk.org/jdk/pull/22649 From joehw at openjdk.org Mon Dec 9 17:44:40 2024 From: joehw at openjdk.org (Joe Wang) Date: Mon, 9 Dec 2024 17:44:40 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files The git query found all those java.xml properties files likely due to the jcheck change (JDK-8325558) you made. That patch correctly kept the copyright years as they were since we generally don't change copyright year unless the change is significant. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2528864312 From mchung at openjdk.org Mon Dec 9 18:01:37 2024 From: mchung at openjdk.org (Mandy Chung) Date: Mon, 9 Dec 2024 18:01:37 GMT Subject: [jdk24] RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 In-Reply-To: References: Message-ID: On Fri, 6 Dec 2024 15:11:20 GMT, Chen Liang wrote: > Hi all, > > This pull request contains a backport of commit [49664195](https://github.com/openjdk/jdk/commit/496641955041c5e48359e6256a4a61812653d900) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository. > > This is a test-only change so it is eligible for backport; in addition, this change is logically part of the Class-File API finalized in JDK 24. > > The commit being backported was authored by Chen Liang on 6 Dec 2024 and was reviewed by Mandy Chung and Adam Sotona. > > Thanks! Marked as reviewed by mchung (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22607#pullrequestreview-2489586744 From prr at openjdk.org Mon Dec 9 18:15:43 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 9 Dec 2024 18:15:43 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: <-CBeobDgFBPLaO0HJADt-SzXLUbrgCDhklHTiElA2RY=.7ec7eede-d6aa-4189-b6f1-5b23250a7512@github.com> On Mon, 9 Dec 2024 12:37:37 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Add more client files There's an image (JPG) file in this list ! Why ? ------------- PR Comment: https://git.openjdk.org/jdk/pull/22638#issuecomment-2528980141 From liach at openjdk.org Mon Dec 9 18:37:42 2024 From: liach at openjdk.org (Chen Liang) Date: Mon, 9 Dec 2024 18:37:42 GMT Subject: [jdk24] RFR: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 In-Reply-To: References: Message-ID: <-vHUTV6ABJZEaxVGeZ2FytzgMEIx-Cdcgm_I5TIuxo4=.5f76bd21-9378-4e52-949b-06ad59192bab@github.com> On Fri, 6 Dec 2024 15:11:20 GMT, Chen Liang wrote: > Hi all, > > This pull request contains a backport of commit [49664195](https://github.com/openjdk/jdk/commit/496641955041c5e48359e6256a4a61812653d900) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository. > > This is a test-only change so it is eligible for backport; in addition, this change is logically part of the Class-File API finalized in JDK 24. > > The commit being backported was authored by Chen Liang on 6 Dec 2024 and was reviewed by Mandy Chung and Adam Sotona. > > Thanks! Thanks for the review! ------------- PR Comment: https://git.openjdk.org/jdk/pull/22607#issuecomment-2529047739 From liach at openjdk.org Mon Dec 9 18:37:43 2024 From: liach at openjdk.org (Chen Liang) Date: Mon, 9 Dec 2024 18:37:43 GMT Subject: [jdk24] Integrated: 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 In-Reply-To: References: Message-ID: On Fri, 6 Dec 2024 15:11:20 GMT, Chen Liang wrote: > Hi all, > > This pull request contains a backport of commit [49664195](https://github.com/openjdk/jdk/commit/496641955041c5e48359e6256a4a61812653d900) from the [openjdk/jdk](https://git.openjdk.org/jdk) repository. > > This is a test-only change so it is eligible for backport; in addition, this change is logically part of the Class-File API finalized in JDK 24. > > The commit being backported was authored by Chen Liang on 6 Dec 2024 and was reviewed by Mandy Chung and Adam Sotona. > > Thanks! This pull request has now been integrated. Changeset: a8132543 Author: Chen Liang URL: https://git.openjdk.org/jdk/commit/a81325433d7da6b73abb37ea3e33489d0a3afbae Stats: 634 lines in 360 files changed: 2 ins; 555 del; 77 mod 8334733: Remove obsolete @enablePreview from tests after JDK-8334714 Reviewed-by: mchung Backport-of: 496641955041c5e48359e6256a4a61812653d900 ------------- PR: https://git.openjdk.org/jdk/pull/22607 From ihse at openjdk.org Mon Dec 9 19:04:44 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 19:04:44 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v2] In-Reply-To: <-CBeobDgFBPLaO0HJADt-SzXLUbrgCDhklHTiElA2RY=.7ec7eede-d6aa-4189-b6f1-5b23250a7512@github.com> References: <-CBeobDgFBPLaO0HJADt-SzXLUbrgCDhklHTiElA2RY=.7ec7eede-d6aa-4189-b6f1-5b23250a7512@github.com> Message-ID: <08brSTaz5WLn_Hv1i0feMAZUYn-GnboDXiKPBZh_VIg=.25d76d8b-3c31-45c1-bfeb-39e5b2ad641d@github.com> On Mon, 9 Dec 2024 18:13:25 GMT, Phil Race wrote: > There's an image (JPG) file in this list ! Why ? That is indeed a very good question. I got a few other modified binary files as well; I can't say why. I am basically doing a sed for `Copyright (c) ... Oracle`, and I have double-checked that there are no such strings in that file. ... ohhh... I think I get it, sed might have mistaken CRLF as line endings and converted it to pure LF. I'll revert it anyway. Thanks for spotting. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22638#issuecomment-2529120261 From ihse at openjdk.org Mon Dec 9 19:11:05 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Mon, 9 Dec 2024 19:11:05 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: Revert mistakenly modified binary files ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22638/files - new: https://git.openjdk.org/jdk/pull/22638/files/e196d3f6..973f9573 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22638&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22638&range=01-02 Stats: 0 lines in 19 files changed: 0 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/22638.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22638/head:pull/22638 PR: https://git.openjdk.org/jdk/pull/22638 From acobbs at openjdk.org Mon Dec 9 19:18:56 2024 From: acobbs at openjdk.org (Archie Cobbs) Date: Mon, 9 Dec 2024 19:18:56 GMT Subject: RFR: 8343478: Remove unnecessary @SuppressWarnings annotations (core-libs) [v8] In-Reply-To: <9ZqHljyJeMr8fPG4-iU6bfQT9hQxTAwrGCl4xsQn3LA=.0b01f899-d849-4e23-8d50-8f186aade664@github.com> References: <9ZqHljyJeMr8fPG4-iU6bfQT9hQxTAwrGCl4xsQn3LA=.0b01f899-d849-4e23-8d50-8f186aade664@github.com> Message-ID: > Please review this patch which removes unnecessary `@SuppressWarnings` annotations. Archie Cobbs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: - Remove more unnecessary suppressions. - Merge branch 'master' into SuppressWarningsCleanup-core-libs - Remove more unnecessary @SuppressWarnings annotations. - Merge branch 'master' into SuppressWarningsCleanup-core-libs - Remove more unnecessary warning suppressions. - Merge branch 'master' into SuppressWarningsCleanup-core-libs - Put back @SuppressWarnings annotations to be fixed by JDK-8343286. - Merge branch 'master' into SuppressWarningsCleanup-core-libs - Update copyright years. - Remove a few more @SuppressWarnings annotations. - ... and 5 more: https://git.openjdk.org/jdk/compare/cc628a13...ee2862e5 ------------- Changes: https://git.openjdk.org/jdk/pull/21852/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=21852&range=07 Stats: 194 lines in 99 files changed: 0 ins; 106 del; 88 mod Patch: https://git.openjdk.org/jdk/pull/21852.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/21852/head:pull/21852 PR: https://git.openjdk.org/jdk/pull/21852 From lancea at openjdk.org Mon Dec 9 19:32:39 2024 From: lancea at openjdk.org (Lance Andersen) Date: Mon, 9 Dec 2024 19:32:39 GMT Subject: RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle debug In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 17:22:14 GMT, Roger Riggs wrote: > Replace broken getProperty with Boolean.getBoolean. > > Manual testing confirms trace messages are enabled with `-Dresource.bundle.debug=true` Marked as reviewed by lancea (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22649#pullrequestreview-2489791907 From eirbjo at openjdk.org Mon Dec 9 19:38:38 2024 From: eirbjo at openjdk.org (Eirik =?UTF-8?B?QmrDuHJzbsO4cw==?=) Date: Mon, 9 Dec 2024 19:38:38 GMT Subject: RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle debug In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 17:22:14 GMT, Roger Riggs wrote: > Replace broken getProperty with Boolean.getBoolean. > > Manual testing confirms trace messages are enabled with `-Dresource.bundle.debug=true` Marked as reviewed by eirbjo (Committer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22649#pullrequestreview-2489826019 From joehw at openjdk.org Mon Dec 9 19:53:38 2024 From: joehw at openjdk.org (Joe Wang) Date: Mon, 9 Dec 2024 19:53:38 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files Marked as reviewed by joehw (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2489899005 From rriggs at openjdk.org Mon Dec 9 21:11:40 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Mon, 9 Dec 2024 21:11:40 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:45:42 GMT, Magnus Ihse Bursie wrote: >> That git query isn't correct for all the files in the repo. In particular, the copyrights on third party files are NOT updated uniformly when new versions are applied. In particular, XML files are NOT updated. > >> That git query isn't correct for all the files in the repo. In particular, the copyrights on third party files are NOT updated uniformly when new versions are applied. In particular, XML files are NOT updated. > > I'm not sure I understand what you mean. Are you saying that I did not update files that should have been updated, or that I updated files that should not have been updated? > > The only 3rd party XML files I know about are the ones in `make/data/cldr`. They have certainly been updated in 2024 from upstream, but they do not carry an Oracle copyright header, so there is nothing there to update. @magicus My question was about third party (xml) code used from Apache. Joe's review and approval resolved that question. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2529462025 From darcy at openjdk.org Mon Dec 9 22:20:40 2024 From: darcy at openjdk.org (Joe Darcy) Date: Mon, 9 Dec 2024 22:20:40 GMT Subject: RFR: 8343478: Remove unnecessary @SuppressWarnings annotations (core-libs) [v8] In-Reply-To: References: <9ZqHljyJeMr8fPG4-iU6bfQT9hQxTAwrGCl4xsQn3LA=.0b01f899-d849-4e23-8d50-8f186aade664@github.com> Message-ID: <1A--E365t_-y1kXsWKb_wotAzGiVatMGWyqjdaLkTK8=.72f824e4-07ae-4e5f-b8cc-713280df230d@github.com> On Mon, 9 Dec 2024 19:18:56 GMT, Archie Cobbs wrote: >> Please review this patch which removes unnecessary `@SuppressWarnings` annotations. > > Archie Cobbs has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 15 commits: > > - Remove more unnecessary suppressions. > - Merge branch 'master' into SuppressWarningsCleanup-core-libs > - Remove more unnecessary @SuppressWarnings annotations. > - Merge branch 'master' into SuppressWarningsCleanup-core-libs > - Remove more unnecessary warning suppressions. > - Merge branch 'master' into SuppressWarningsCleanup-core-libs > - Put back @SuppressWarnings annotations to be fixed by JDK-8343286. > - Merge branch 'master' into SuppressWarningsCleanup-core-libs > - Update copyright years. > - Remove a few more @SuppressWarnings annotations. > - ... and 5 more: https://git.openjdk.org/jdk/compare/cc628a13...ee2862e5 Core reflection changes look fine; thanks for the cleanup @archiecobbs . ------------- Marked as reviewed by darcy (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/21852#pullrequestreview-2490237853 From jlu at openjdk.org Mon Dec 9 23:01:39 2024 From: jlu at openjdk.org (Justin Lu) Date: Mon, 9 Dec 2024 23:01:39 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files Looked at the i18n changes (src, test, and 3rd party icu files w/ Oracle header) and they look correct to me. ------------- Marked as reviewed by jlu (Committer). PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2490302089 From psadhukhan at openjdk.org Tue Dec 10 02:52:43 2024 From: psadhukhan at openjdk.org (Prasanta Sadhukhan) Date: Tue, 10 Dec 2024 02:52:43 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 19:11:05 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert mistakenly modified binary files src/jdk.accessibility/windows/man/jabswitch.md line 3: > 1: --- > 2: # Copyright (c) 2019, 2024, Oracle and/or its affiliates. All rights reserved. > 3: # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. I guess this was committed 3 weeks ago, so shouldn't it be just 2024? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22638#discussion_r1877170365 From ihse at openjdk.org Tue Dec 10 08:50:41 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Tue, 10 Dec 2024 08:50:41 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Tue, 10 Dec 2024 02:50:18 GMT, Prasanta Sadhukhan wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: >> >> Revert mistakenly modified binary files > > src/jdk.accessibility/windows/man/jabswitch.md line 3: > >> 1: --- >> 2: # Copyright (c) 2019, 2024, Oracle and/or its affiliates. All rights reserved. >> 3: # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. > > I guess this was committed 3 weeks ago, so shouldn't it be just 2024? The file existed before, but in the Oracle-only closed repo. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22638#discussion_r1877608909 From psadhukhan at openjdk.org Tue Dec 10 09:04:39 2024 From: psadhukhan at openjdk.org (Prasanta Sadhukhan) Date: Tue, 10 Dec 2024 09:04:39 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 19:11:05 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert mistakenly modified binary files Marked as reviewed by psadhukhan (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22638#pullrequestreview-2491516974 From psadhukhan at openjdk.org Tue Dec 10 09:04:41 2024 From: psadhukhan at openjdk.org (Prasanta Sadhukhan) Date: Tue, 10 Dec 2024 09:04:41 GMT Subject: RFR: 8345797: Update copyright year to 2024 for client-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: <-6Df1pwq9YbsxOYNxM_JJtLxLiU-j0yKeinp4gBDVbI=.bedd6e2a-a7f0-4de2-ab48-1ea46e168e66@github.com> On Tue, 10 Dec 2024 08:47:50 GMT, Magnus Ihse Bursie wrote: >> src/jdk.accessibility/windows/man/jabswitch.md line 3: >> >>> 1: --- >>> 2: # Copyright (c) 2019, 2024, Oracle and/or its affiliates. All rights reserved. >>> 3: # DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. >> >> I guess this was committed 3 weeks ago, so shouldn't it be just 2024? > > The file existed before, but in the Oracle-only closed repo. ok..LGTM ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22638#discussion_r1877641673 From psadhukhan at openjdk.org Tue Dec 10 09:33:39 2024 From: psadhukhan at openjdk.org (Prasanta Sadhukhan) Date: Tue, 10 Dec 2024 09:33:39 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: <0IesHKVS6gy8WPLSFCevvtbtchywwafjo_iChBhuvds=.b02be63c-a28f-47a8-80d3-8293993d9c15@github.com> On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files not sure why client label is added, no java.desktop/accessibility files are in there ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2530994967 From rriggs at openjdk.org Tue Dec 10 15:19:42 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 10 Dec 2024 15:19:42 GMT Subject: Integrated: 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 17:22:14 GMT, Roger Riggs wrote: > Replace broken getProperty with Boolean.getBoolean. > > Manual testing confirms trace messages are enabled with `-Dresource.bundle.debug=true` This pull request has now been integrated. Changeset: 4f855d13 Author: Roger Riggs URL: https://git.openjdk.org/jdk/commit/4f855d1342d55aeee93b7d0c5796fbfd4994c856 Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug Reviewed-by: lancea, eirbjo ------------- PR: https://git.openjdk.org/jdk/pull/22649 From rriggs at openjdk.org Tue Dec 10 15:37:20 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Tue, 10 Dec 2024 15:37:20 GMT Subject: [jdk24] RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug Message-ID: Backport this trivial fix to parsing of the system property "resource.bundle.debug" to jdk24. ------------- Commit messages: - Backport 4f855d1342d55aeee93b7d0c5796fbfd4994c856 Changes: https://git.openjdk.org/jdk/pull/22664/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22664&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345818 Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22664.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22664/head:pull/22664 PR: https://git.openjdk.org/jdk/pull/22664 From prr at openjdk.org Tue Dec 10 21:11:39 2024 From: prr at openjdk.org (Phil Race) Date: Tue, 10 Dec 2024 21:11:39 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: <0IesHKVS6gy8WPLSFCevvtbtchywwafjo_iChBhuvds=.b02be63c-a28f-47a8-80d3-8293993d9c15@github.com> References: <0IesHKVS6gy8WPLSFCevvtbtchywwafjo_iChBhuvds=.b02be63c-a28f-47a8-80d3-8293993d9c15@github.com> Message-ID: 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 From mli at openjdk.org Wed Dec 11 09:40:38 2024 From: mli at openjdk.org (Hamlin Li) Date: Wed, 11 Dec 2024 09:40:38 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files Nice batch cleanup. ------------- Marked as reviewed by mli (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2494928848 From lancea at openjdk.org Wed Dec 11 11:41:40 2024 From: lancea at openjdk.org (Lance Andersen) Date: Wed, 11 Dec 2024 11:41:40 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 15:42:57 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list >> >> and then run a script to update the copyright year to 2024 on these files. >> >> I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. > > Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: > > Revert changes to binary files Marked as reviewed by lancea (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22640#pullrequestreview-2495330243 From ihse at openjdk.org Wed Dec 11 21:10:52 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 11 Dec 2024 21:10:52 GMT Subject: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v3] In-Reply-To: <0IesHKVS6gy8WPLSFCevvtbtchywwafjo_iChBhuvds=.b02be63c-a28f-47a8-80d3-8293993d9c15@github.com> References: <0IesHKVS6gy8WPLSFCevvtbtchywwafjo_iChBhuvds=.b02be63c-a28f-47a8-80d3-8293993d9c15@github.com> Message-ID: On Tue, 10 Dec 2024 09:31:21 GMT, Prasanta Sadhukhan wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one additional commit since the last revision: >> >> Revert changes to binary files > > not sure why client label is added, no java.desktop/accessibility files are in there @prsadhuk @prrace `src/java.base/share/classes/jdk/internal/access/JavaAWTFontAccess.java` matches the pattern `"src/java.base/share/classes/jdk/internal/access/\\w+AWT"` which is setup for `client` in the Skara `jdk.json` label configuration. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22640#issuecomment-2537183864 From ihse at openjdk.org Wed Dec 11 21:10:53 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 11 Dec 2024 21:10:53 GMT Subject: Integrated: 8345799: Update copyright year to 2024 for core-libs in files where it was missed In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 12:30:19 GMT, Magnus Ihse Bursie wrote: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. This pull request has now been integrated. Changeset: ddf04617 Author: Magnus Ihse Bursie URL: https://git.openjdk.org/jdk/commit/ddf04617887dc389cd7667e820da7ac91eea9e8c Stats: 441 lines in 441 files changed: 0 ins; 0 del; 441 mod 8345799: Update copyright year to 2024 for core-libs in files where it was missed Reviewed-by: joehw, jlu, mli, lancea, kevinw ------------- PR: https://git.openjdk.org/jdk/pull/22640 From ihse at openjdk.org Wed Dec 11 21:32:44 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 11 Dec 2024 21:32:44 GMT Subject: Integrated: 8345797: Update copyright year to 2024 for client-libs in files where it was missed In-Reply-To: References: Message-ID: On Mon, 9 Dec 2024 12:16:26 GMT, Magnus Ihse Bursie wrote: > Some files have been modified in 2024, but the copyright year has not been properly updated. This should be fixed. > > I have located these modified files using: > > git log --since="Jan 1" --name-only --pretty=format: | sort -u > file.list > > and then run a script to update the copyright year to 2024 on these files. > > I have made a manual sampling of files in the list to verify that they have indeed been modified in 2024. This pull request has now been integrated. Changeset: 64fad1c7 Author: Magnus Ihse Bursie URL: https://git.openjdk.org/jdk/commit/64fad1c7d374bbc635bad3b1fa7941379f39565f Stats: 342 lines in 342 files changed: 0 ins; 0 del; 342 mod 8345797: Update copyright year to 2024 for client-libs in files where it was missed Reviewed-by: psadhukhan ------------- PR: https://git.openjdk.org/jdk/pull/22638 From rriggs at openjdk.org Thu Dec 12 15:48:39 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Thu, 12 Dec 2024 15:48:39 GMT Subject: [jdk24] RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug In-Reply-To: References: Message-ID: On Tue, 10 Dec 2024 15:31:08 GMT, Roger Riggs wrote: > Backport this trivial fix to parsing of the system property "resource.bundle.debug" to jdk24. @LanceAndersen Please review ------------- PR Comment: https://git.openjdk.org/jdk/pull/22664#issuecomment-2539329603 From lancea at openjdk.org Thu Dec 12 17:24:38 2024 From: lancea at openjdk.org (Lance Andersen) Date: Thu, 12 Dec 2024 17:24:38 GMT Subject: [jdk24] RFR: 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug In-Reply-To: References: Message-ID: On Tue, 10 Dec 2024 15:31:08 GMT, Roger Riggs wrote: > Backport this trivial fix to parsing of the system property "resource.bundle.debug" to jdk24. Marked as reviewed by lancea (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/22664#pullrequestreview-2500333810 From rriggs at openjdk.org Thu Dec 12 17:30:44 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Thu, 12 Dec 2024 17:30:44 GMT Subject: [jdk24] Integrated: 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug In-Reply-To: References: Message-ID: <9dMt0wB4pGO9tmIjgxbPNj5RhXSMx1oZcdBk0a7VV1U=.5e87d68c-3532-4ee7-b85e-f79108a6398b@github.com> On Tue, 10 Dec 2024 15:31:08 GMT, Roger Riggs wrote: > Backport this trivial fix to parsing of the system property "resource.bundle.debug" to jdk24. This pull request has now been integrated. Changeset: 3b53ed7f Author: Roger Riggs URL: https://git.openjdk.org/jdk/commit/3b53ed7fb000d108bc4e98224d2db9322d8263a4 Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod 8345818: Fix SM cleanup of parsing of System property resource.bundle.debug Reviewed-by: lancea Backport-of: 4f855d1342d55aeee93b7d0c5796fbfd4994c856 ------------- PR: https://git.openjdk.org/jdk/pull/22664 From isipka at openjdk.org Thu Dec 12 17:31:12 2024 From: isipka at openjdk.org (Ivan =?UTF-8?B?xaBpcGth?=) Date: Thu, 12 Dec 2024 17:31:12 GMT Subject: RFR: 8346117: added @test annotations Message-ID: @mahendrachhipa @bwhuang-us @serhiysachkov ------------- Commit messages: - added @test annotations Changes: https://git.openjdk.org/jdk/pull/22717/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22717&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8346117 Stats: 2 lines in 2 files changed: 2 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/22717.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22717/head:pull/22717 PR: https://git.openjdk.org/jdk/pull/22717 From shurailine at openjdk.org Thu Dec 12 17:41:37 2024 From: shurailine at openjdk.org (Alexandre Iline) Date: Thu, 12 Dec 2024 17:41:37 GMT Subject: RFR: 8346117: Add test annotation In-Reply-To: References: Message-ID: On Thu, 12 Dec 2024 16:59:58 GMT, Ivan ?ipka wrote: > @mahendrachhipa @bwhuang-us @serhiysachkov It would make sense to at least run these tests on all supported platforms to make sure nothing wrong with them. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22717#issuecomment-2539596629 From ihse at openjdk.org Wed Dec 18 17:06:02 2024 From: ihse at openjdk.org (Magnus Ihse Bursie) Date: Wed, 18 Dec 2024 17:06:02 GMT Subject: RFR: 8344191: Build code should not have classpath exception [v2] In-Reply-To: References: Message-ID: > In several (most? all?) of the build system files, the copyright header includes the classpath exception. This makes no sense, and should be removed. > > I have removed the classpath exception from makefiles, autoconf, shell scripts, properties files, configuration files, IDE support files, build tools and data. > > The only places where the classpath exception is still kept in the make directory is as text strings in some build tools, which generate source code that is bundled with `src.zip`, and thus *must* have the classpath exception. > > This is a huge and autogenerated, but content-wise trivial, PR, and I know such are hard to review. I recommend looking at the entire diff file instead of checking this file-by-file in the Github web GUI. (That's bound to be a painful experience) Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains three commits: - Merge branch 'master' into remove-build-classpath-exception - Update build tools, data and IDE support - Update makefiles, autoconf, shell scripts, properties files and configuration files ------------- Changes: https://git.openjdk.org/jdk/pull/22104/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22104&range=01 Stats: 1994 lines in 555 files changed: 0 ins; 1120 del; 874 mod Patch: https://git.openjdk.org/jdk/pull/22104.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22104/head:pull/22104 PR: https://git.openjdk.org/jdk/pull/22104 From asemenyuk at openjdk.org Wed Dec 18 18:58:40 2024 From: asemenyuk at openjdk.org (Alexey Semenyuk) Date: Wed, 18 Dec 2024 18:58:40 GMT Subject: RFR: 8344191: Build code should not have classpath exception [v2] In-Reply-To: References: Message-ID: On Wed, 18 Dec 2024 17:06:02 GMT, Magnus Ihse Bursie wrote: >> In several (most? all?) of the build system files, the copyright header includes the classpath exception. This makes no sense, and should be removed. >> >> I have removed the classpath exception from makefiles, autoconf, shell scripts, properties files, configuration files, IDE support files, build tools and data. >> >> The only places where the classpath exception is still kept in the make directory is as text strings in some build tools, which generate source code that is bundled with `src.zip`, and thus *must* have the classpath exception. >> >> This is a huge and autogenerated, but content-wise trivial, PR, and I know such are hard to review. I recommend looking at the entire diff file instead of checking this file-by-file in the Github web GUI. (That's bound to be a painful experience) > > Magnus Ihse Bursie has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains three commits: > > - Merge branch 'master' into remove-build-classpath-exception > - Update build tools, data and IDE support > - Update makefiles, autoconf, shell scripts, properties files and configuration files jpackage changes look good. $0.02 ------------- Marked as reviewed by asemenyuk (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22104#pullrequestreview-2512625117 From naoto at openjdk.org Thu Dec 19 22:18:16 2024 From: naoto at openjdk.org (Naoto Sato) Date: Thu, 19 Dec 2024 22:18:16 GMT Subject: RFR: 8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc Message-ID: Clarifying the documentation of `DateTimeFormatterBuilder.appendZoneId()` and similar methods to align the description with the behavior, in which `ZoneOffset` is only parsed from the formatter for offset texts without any prefixes. Corresponding CSR has also been drafted. ------------- Commit messages: - initial commit Changes: https://git.openjdk.org/jdk/pull/22837/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22837&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8175709 Stats: 34 lines in 1 file changed: 0 ins; 0 del; 34 mod Patch: https://git.openjdk.org/jdk/pull/22837.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22837/head:pull/22837 PR: https://git.openjdk.org/jdk/pull/22837 From rriggs at openjdk.org Fri Dec 20 17:11:35 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Fri, 20 Dec 2024 17:11:35 GMT Subject: RFR: 8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc In-Reply-To: References: Message-ID: On Thu, 19 Dec 2024 22:12:52 GMT, Naoto Sato wrote: > Clarifying the documentation of `DateTimeFormatterBuilder.appendZoneId()` and similar methods to align the description with the behavior, in which `ZoneOffset` is only parsed from the formatter for offset texts without any prefixes. Corresponding CSR has also been drafted. src/java.base/share/classes/java/time/format/DateTimeFormatterBuilder.java line 1154: > 1152: * offset-based zone and will not match region-based zones. The offset > 1153: * ID parsing is equivalent to using {@link #appendOffset(String, String)} > 1154: * using the arguments 'HH:MM:ss' and the no offset string '0'. The change to drop UT, UTC, GMT, from offset parsing, looks to be correct. However, it does accept parsing of the offset formatted strings in contradiction to the 2nd paragraph above. ``` * This appends an instruction to format/parse the zone ID to the builder * only if it is a region-based ID. This pre-existing text is also isn't clear in that the formatter is always appended to the builder. The accepting only of a region-based ID occurs when the DateTimeFormatter.parse(...) is parsing. Perhaps a separate clarification may be useful ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22837#discussion_r1894185376 From naoto at openjdk.org Fri Dec 20 18:12:17 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 18:12:17 GMT Subject: RFR: 8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc [v2] In-Reply-To: References: Message-ID: <5HcT8q1Ais4MPisgJy8EQLH4ZIGjepWPMm31JU45C4c=.d4cd0e34-711f-4234-b269-888a46fb1eb3@github.com> > Clarifying the documentation of `DateTimeFormatterBuilder.appendZoneId()` and similar methods to align the description with the behavior, in which `ZoneOffset` is only parsed from the formatter for offset texts without any prefixes. Corresponding CSR has also been drafted. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Reflects review comments ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22837/files - new: https://git.openjdk.org/jdk/pull/22837/files/36d3e8c7..5439c2c8 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22837&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22837&range=00-01 Stats: 3 lines in 1 file changed: 0 ins; 1 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/22837.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22837/head:pull/22837 PR: https://git.openjdk.org/jdk/pull/22837 From naoto at openjdk.org Fri Dec 20 18:14:37 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 18:14:37 GMT Subject: RFR: 8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc [v2] In-Reply-To: References: Message-ID: <8LAMUrBjAylFP-crB8jP_zZKrZDyj0u2j_xtUlb61Vg=.2f5326e2-9fb6-46c3-8a82-28d379465601@github.com> On Fri, 20 Dec 2024 17:09:26 GMT, Roger Riggs wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Reflects review comments > > src/java.base/share/classes/java/time/format/DateTimeFormatterBuilder.java line 1154: > >> 1152: * offset-based zone and will not match region-based zones. The offset >> 1153: * ID parsing is equivalent to using {@link #appendOffset(String, String)} >> 1154: * using the arguments 'HH:MM:ss' and the no offset string '0'. > > The change to drop UT, UTC, GMT, from offset parsing, looks to be correct. > However, it does accept parsing of the offset formatted strings in contradiction to the 2nd paragraph above. > ``` > * This appends an instruction to format/parse the zone ID to the builder > * only if it is a region-based ID. > > This pre-existing text is also isn't clear in that the formatter is always appended to the builder. > The accepting only of a region-based ID occurs when the DateTimeFormatter.parse(...) is parsing. > Perhaps a separate clarification may be useful Thanks, Roger. Updated the description per your suggestion. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22837#discussion_r1894246676 From naoto at openjdk.org Fri Dec 20 19:59:50 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 19:59:50 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression Message-ID: The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. ------------- Commit messages: - initial commit Changes: https://git.openjdk.org/jdk/pull/22854/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22854&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8345668 Stats: 78 lines in 4 files changed: 69 ins; 0 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/22854.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22854/head:pull/22854 PR: https://git.openjdk.org/jdk/pull/22854 From rriggs at openjdk.org Fri Dec 20 20:29:34 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Fri, 20 Dec 2024 20:29:34 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 19:55:06 GMT, Naoto Sato wrote: > The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. src/java.base/share/classes/java/time/ZoneOffset.java line 432: > 430: result = new ZoneOffset(totalSeconds); > 431: SECONDS_CACHE.putIfAbsent(totalSecs, result); > 432: result = SECONDS_CACHE.get(totalSecs); putIfAbsent() returns the existing value (if any), the 2nd get can be avoided by using the non-null value if returned or returning the result just created. Suggestion: var existing = SECONDS_CACHE.putIfAbsent(totalSecs, result); return (existing != null) ? existing : result; It should perform better than doing the `get` again. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894362437 From naoto at openjdk.org Fri Dec 20 20:58:22 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 20:58:22 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v2] In-Reply-To: References: Message-ID: > The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Update src/java.base/share/classes/java/time/ZoneOffset.java Co-authored-by: Roger Riggs ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22854/files - new: https://git.openjdk.org/jdk/pull/22854/files/3df7e9f1..1e09b8be Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22854&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22854&range=00-01 Stats: 2 lines in 1 file changed: 0 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/22854.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22854/head:pull/22854 PR: https://git.openjdk.org/jdk/pull/22854 From naoto at openjdk.org Fri Dec 20 20:58:22 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 20:58:22 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v2] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 20:25:28 GMT, Roger Riggs wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Update src/java.base/share/classes/java/time/ZoneOffset.java >> >> Co-authored-by: Roger Riggs > > src/java.base/share/classes/java/time/ZoneOffset.java line 432: > >> 430: result = new ZoneOffset(totalSeconds); >> 431: SECONDS_CACHE.putIfAbsent(totalSecs, result); >> 432: result = SECONDS_CACHE.get(totalSecs); > > putIfAbsent() returns the existing value (if any), the 2nd get can be avoided by using the non-null value if returned or returning the result just created. > Suggestion: > > var existing = SECONDS_CACHE.putIfAbsent(totalSecs, result); > return (existing != null) ? existing : result; > > It should perform better than doing the `get` again. That's right. Committed as suggested ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894382433 From naoto at openjdk.org Fri Dec 20 21:06:16 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 21:06:16 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: > The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: Fixed compile error ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22854/files - new: https://git.openjdk.org/jdk/pull/22854/files/1e09b8be..8dca103a Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22854&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22854&range=01-02 Stats: 3 lines in 1 file changed: 2 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22854.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22854/head:pull/22854 PR: https://git.openjdk.org/jdk/pull/22854 From rriggs at openjdk.org Fri Dec 20 22:52:35 2024 From: rriggs at openjdk.org (Roger Riggs) Date: Fri, 20 Dec 2024 22:52:35 GMT Subject: RFR: 8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc [v2] In-Reply-To: <5HcT8q1Ais4MPisgJy8EQLH4ZIGjepWPMm31JU45C4c=.d4cd0e34-711f-4234-b269-888a46fb1eb3@github.com> References: <5HcT8q1Ais4MPisgJy8EQLH4ZIGjepWPMm31JU45C4c=.d4cd0e34-711f-4234-b269-888a46fb1eb3@github.com> Message-ID: On Fri, 20 Dec 2024 18:12:17 GMT, Naoto Sato wrote: >> Clarifying the documentation of `DateTimeFormatterBuilder.appendZoneId()` and similar methods to align the description with the behavior, in which `ZoneOffset` is only parsed from the formatter for offset texts without any prefixes. Corresponding CSR has also been drafted. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Reflects review comments lgtm ------------- Marked as reviewed by rriggs (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22837#pullrequestreview-2518472240 From swen at openjdk.org Fri Dec 20 23:07:35 2024 From: swen at openjdk.org (Shaojin Wen) Date: Fri, 20 Dec 2024 23:07:35 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 21:06:16 GMT, Naoto Sato wrote: >> The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Fixed compile error src/java.base/share/classes/java/time/ZoneOffset.java line 428: > 426: if (totalSeconds % (15 * SECONDS_PER_MINUTE) == 0) { > 427: Integer totalSecs = totalSeconds; > 428: ZoneOffset result = SECONDS_CACHE.get(totalSecs); Here, each call may allocate an Integer object. The maximum number of ZoneOffsets that need to be cached here is only 148. Using AtomicReferenceArray is better than AtomicConcurrentHashMap. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894486852 From swen at openjdk.org Fri Dec 20 23:10:53 2024 From: swen at openjdk.org (Shaojin Wen) Date: Fri, 20 Dec 2024 23:10:53 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 23:05:06 GMT, Shaojin Wen wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Fixed compile error > > src/java.base/share/classes/java/time/ZoneOffset.java line 428: > >> 426: if (totalSeconds % (15 * SECONDS_PER_MINUTE) == 0) { >> 427: Integer totalSecs = totalSeconds; >> 428: ZoneOffset result = SECONDS_CACHE.get(totalSecs); > > Here, each call may allocate an Integer object. The maximum number of ZoneOffsets that need to be cached here is only 148. Using AtomicReferenceArray is better than AtomicConcurrentHashMap. For example: static final class Cache { static final AtomicReferenceArray MINUTES_15_CACHE = new AtomicReferenceArray<>(18 * 2 * 4); } public static ZoneOffset ofTotalSeconds(int totalSeconds) { // ... int minutes15Rem = totalSeconds / (15 * SECONDS_PER_MINUTE); if (totalSeconds - minutes15Rem * 15 * SECONDS_PER_MINUTE == 0) { int cacheIndex = minutes15Rem + 18; ZoneOffset result = Cache.MINUTES_15_CACHE.get(cacheIndex); if (result == null) { result = new ZoneOffset(totalSeconds); if (!Cache.MINUTES_15_CACHE.compareAndSet(cacheIndex, null, result)) { result = Cache.MINUTES_15_CACHE.get(minutes15Rem); } } return result; } // ... } ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894488013 From naoto at openjdk.org Fri Dec 20 23:51:36 2024 From: naoto at openjdk.org (Naoto Sato) Date: Fri, 20 Dec 2024 23:51:36 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 23:07:47 GMT, Shaojin Wen wrote: >> src/java.base/share/classes/java/time/ZoneOffset.java line 428: >> >>> 426: if (totalSeconds % (15 * SECONDS_PER_MINUTE) == 0) { >>> 427: Integer totalSecs = totalSeconds; >>> 428: ZoneOffset result = SECONDS_CACHE.get(totalSecs); >> >> Here, each call may allocate an Integer object. The maximum number of ZoneOffsets that need to be cached here is only 148. Using AtomicReferenceArray is better than AtomicConcurrentHashMap. > > For example: > > static final AtomicReferenceArray MINUTES_15_CACHE = new AtomicReferenceArray<>(37 * 4); > > public static ZoneOffset ofTotalSeconds(int totalSeconds) { > // ... > int minutes15Rem = totalSeconds / (15 * SECONDS_PER_MINUTE); > if (totalSeconds - minutes15Rem * 15 * SECONDS_PER_MINUTE == 0) { > int cacheIndex = minutes15Rem + 18 * 4; > ZoneOffset result = MINUTES_15_CACHE.get(cacheIndex); > if (result == null) { > result = new ZoneOffset(totalSeconds); > if (!MINUTES_15_CACHE.compareAndSet(cacheIndex, null, result)) { > result = MINUTES_15_CACHE.get(minutes15Rem); > } > } > return result; > } > // ... > } Hi Shaojin, Thanks for the suggestion, but I am not planning to improve the code more than backing out the offending fix at this time. (btw, cache size would be 149 as 18:00 and -18:00 are inclusive) ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894505406 From swen at openjdk.org Sat Dec 21 00:02:35 2024 From: swen at openjdk.org (Shaojin Wen) Date: Sat, 21 Dec 2024 00:02:35 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 23:46:57 GMT, Naoto Sato wrote: >> For example: >> >> static final AtomicReferenceArray MINUTES_15_CACHE = new AtomicReferenceArray<>(37 * 4); >> >> public static ZoneOffset ofTotalSeconds(int totalSeconds) { >> // ... >> int minutes15Rem = totalSeconds / (15 * SECONDS_PER_MINUTE); >> if (totalSeconds - minutes15Rem * 15 * SECONDS_PER_MINUTE == 0) { >> int cacheIndex = minutes15Rem + 18 * 4; >> ZoneOffset result = MINUTES_15_CACHE.get(cacheIndex); >> if (result == null) { >> result = new ZoneOffset(totalSeconds); >> if (!MINUTES_15_CACHE.compareAndSet(cacheIndex, null, result)) { >> result = MINUTES_15_CACHE.get(minutes15Rem); >> } >> } >> return result; >> } >> // ... >> } > > Hi Shaojin, > Thanks for the suggestion, but I am not planning to improve the code more than backing out the offending fix at this time. (btw, cache size would be 149 as 18:00 and -18:00 are inclusive) Can I submit a PR to make this improvement? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894509276 From liach at openjdk.org Sat Dec 21 00:45:35 2024 From: liach at openjdk.org (Chen Liang) Date: Sat, 21 Dec 2024 00:45:35 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 23:59:30 GMT, Shaojin Wen wrote: >> Hi Shaojin, >> Thanks for the suggestion, but I am not planning to improve the code more than backing out the offending fix at this time. (btw, cache size would be 149 as 18:00 and -18:00 are inclusive) > > Can I submit a PR to make this improvement? @wenshao I agree with your proposal. Also for this part: ZoneOffset result = MINUTES_15_CACHE.get(cacheIndex); if (result == null) { result = new ZoneOffset(totalSeconds); if (!MINUTES_15_CACHE.compareAndSet(cacheIndex, null, result)) { result = MINUTES_15_CACHE.get(minutes15Rem); } } I recommend a rewrite: ZoneOffset result = MINUTES_15_CACHE.getPlain(cacheIndex); if (result == null) { result = new ZoneOffset(totalSeconds); ZoneOffset existing = MINUTES_15_CACHE.compareAndExchange(cacheIndex, null, result); return existing == null ? result : existing; } The `getPlain` is safe because `ZoneOffset` is thread safe, so you can use the object when you can observe a `ZoneOffset` object reference. Also `compareAndExchange` avoids extra operations if we failed to racily set the computed `ZoneOffset`. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894520408 From liach at openjdk.org Sat Dec 21 00:59:42 2024 From: liach at openjdk.org (Chen Liang) Date: Sat, 21 Dec 2024 00:59:42 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 21:06:16 GMT, Naoto Sato wrote: >> The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Fixed compile error Changes requested by liach (Reviewer). The `putIfAbsent` remark from Roger Riggs applies to `DateTimeTextProvider` and `DecimalStyle` too. I think reusing existing result in these two places is beneficial, as the replaced `computeIfAbsent` returns the same object identity which may be helpful for quick `equals` comparisons. test/micro/org/openjdk/bench/java/time/ZoneOffsetBench.java line 49: > 47: public void ofTotalSeconds() { > 48: for (int i = 0; i < 1_000; i++) { > 49: ZoneOffset.ofTotalSeconds(0); This benchmark method should accept a `Blackhole`, and the return value of `ofTotalSeconds` must be sent to the `Blackhole.consume` method. ------------- PR Review: https://git.openjdk.org/jdk/pull/22854#pullrequestreview-2518538592 PR Comment: https://git.openjdk.org/jdk/pull/22854#issuecomment-2557926553 PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894522864 From liach at openjdk.org Sat Dec 21 01:02:35 2024 From: liach at openjdk.org (Chen Liang) Date: Sat, 21 Dec 2024 01:02:35 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: <5bjf0rolvoU_PbPLWY7F2OLgeHiN46goT3tPyqzmM0g=.0d6dafd5-e045-4b79-ac5e-76a256a910d7@github.com> On Sat, 21 Dec 2024 00:54:34 GMT, Chen Liang wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Fixed compile error > > test/micro/org/openjdk/bench/java/time/ZoneOffsetBench.java line 49: > >> 47: public void ofTotalSeconds() { >> 48: for (int i = 0; i < 1_000; i++) { >> 49: ZoneOffset.ofTotalSeconds(0); > > This benchmark method should accept a `Blackhole`, and the return value of `ofTotalSeconds` must be sent to the `Blackhole.consume` method. This benchmark currently works probably because the cache interactions in `ofTotalSeconds`, which means JIT compilation cannot prove it is side-effect free. Had it been as simple as a decimal computation or if the cache becomes a stable map, JIT compilation can eliminate the static factory method call entirely, and the benchmark would be measuring the performance of no-op invocation. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1894523813 From qxing at openjdk.org Mon Dec 23 09:50:10 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Mon, 23 Dec 2024 09:50:10 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files Message-ID: This patch fixes unmatched brackets in some source files. ------------- Commit messages: - Fix unmatched brackets in source files. Changes: https://git.openjdk.org/jdk/pull/22861/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=22861&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8346773 Stats: 2244 lines in 25 files changed: 2211 ins; 2 del; 31 mod Patch: https://git.openjdk.org/jdk/pull/22861.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22861/head:pull/22861 PR: https://git.openjdk.org/jdk/pull/22861 From erikj at openjdk.org Mon Dec 23 14:05:35 2024 From: erikj at openjdk.org (Erik Joelsson) Date: Mon, 23 Dec 2024 14:05:35 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 09:45:00 GMT, Qizheng Xing wrote: > This patch fixes unmatched brackets in some source files. I can really only review the doc files and the Makefile. doc/hotspot-unit-tests.md line 175: > 173: there is no need to have them in error messages. Asserts print only > 174: compared values, they do not print any of interim variables, e.g. > 175: `ASSERT_TRUE(val1 == val2 && isFail(foo(8)) || i == 18)` prints only Looking at this expression, I believe the intention is this. Suggestion: `ASSERT_TRUE((val1 == val2 && isFail(foo(8))) || i == 18)` prints only ------------- PR Review: https://git.openjdk.org/jdk/pull/22861#pullrequestreview-2520648246 PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1895785097 From jlu at openjdk.org Mon Dec 23 17:13:36 2024 From: jlu at openjdk.org (Justin Lu) Date: Mon, 23 Dec 2024 17:13:36 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 09:45:00 GMT, Qizheng Xing wrote: > This patch fixes unmatched brackets in some source files. make/data/cldr/common/main/kn.xml line 1085: > 1083: ????????? ?????????? > 1084: ?????????-?????? ?????????? > 1085: ?????????? ??????????? (???? ???????, ????????) Hi, we would not modify the contents of upstream data from CLDR. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1895964999 From kbarrett at openjdk.org Mon Dec 23 19:36:36 2024 From: kbarrett at openjdk.org (Kim Barrett) Date: Mon, 23 Dec 2024 19:36:36 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 09:45:00 GMT, Qizheng Xing wrote: > This patch fixes unmatched brackets in some source files. I strongly suggest avoiding omnibus changes like this when possible (which it is here). Just because it's all about one "kind" of change doesn't make it a cohesive change. This is touching many distinct areas of the JDK, and several different languages as well. 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 the whole thing might get stalled by discussion of one piece. There is also no mention of what testing has been done for this PR. Some of the changes are in executable code, and need to be tested. I think that all of the files in make/data/cldr/common are from the Unicode Consortium, and should not be modified here. doc/hotspot-unit-tests.html line 248: > 246: so there is no need to have them in error messages. Asserts print only > 247: compared values, they do not print any of interim variables, e.g. > 248: ASSERT_TRUE(val1 == val2 && isFail(foo(8)) || i == 18) This file is generated from the .md file, and should not be edited directly. test/hotspot/jtreg/testlibrary/ctw/Makefile line 50: > 48: $(TESTLIBRARY_DIR)/jdk/test/lib/util \ > 49: $(TESTLIBRARY_DIR)/jtreg \ > 50: -maxdepth 1 -name '*.java') I wonder why this hasn't caused problems and been found long ago? Does make just drop that stray close-paren? test/jaxp/javax/xml/jaxp/unittest/transform/Bug8169112.xsl line 65: > 63: @page { margin: 0.1in; } > 64: > 65: } Does this affect the behavior of the test this is part of? test/jdk/sanity/client/lib/SwingSet3/src/com/sun/swingset3/demos/table/resources/oscars.xml line 2: > 1: > 2: 1: > 2: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 19:33:36 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 right before Christmas. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22861#issuecomment-2560215378 From prr at openjdk.org Mon Dec 23 20:33:36 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 23 Dec 2024 20:33:36 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: 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: > Does this change affect the behavior of the associated test(s)? I was also wondering how this was tested. > test/jdk/sanity/client/lib/SwingSet3/src/com/sun/swingset3/demos/table/resources/oscars.xml line 2: > >> 1: >> 2: > I can't tell whether anything was changed in this file other than the modification of all the end of > line indicators. I've no idea whether changing those is appropriate or not, but this file came from > a 3rd party, so might not be appropriate to change here. +1 to all of that. This change is un-reviewable. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896100629 PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896100936 From prr at openjdk.org Mon Dec 23 20:33:34 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 23 Dec 2024 20:33:34 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: 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 right before Christmas. I think at the very least this needs multiple reviewers. Even 2 isn't enough considering it is so cross-area. It went to 7 different mailing lists, so that should tell you something ! ------------- PR Comment: https://git.openjdk.org/jdk/pull/22861#issuecomment-2560263514 From prr at openjdk.org Mon Dec 23 22:18:35 2024 From: prr at openjdk.org (Phil Race) Date: Mon, 23 Dec 2024 22:18:35 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files In-Reply-To: References: Message-ID: <_AIqmu61ZK3rRO-44sivWfkuH1ceJm8bQ3MtL2cu8vs=.f4c3bb3b-3697-4ba4-8199-0f1cf9f2f047@github.com> 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: > >> Does this change affect the behavior of the associated test(s)? > > I was also wondering how this was tested. FYI, the way to test this is .. cd test/jdk jtreg sanity/client/SwingSet/src/TableDemoTest.java I tried converting all ^M to \n in this file another repo and comparing with your patch but every line was different so I just can't review this. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896162028 From qxing at openjdk.org Tue Dec 24 03:26:23 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:26:23 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: Message-ID: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> > This patch fixes unmatched brackets in some source files. Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). - Do not touch files in test. - Do not touch upstream data from CLDR. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22861/files - new: https://git.openjdk.org/jdk/pull/22861/files/540312c4..ec3e6aa5 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22861&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22861&range=00-01 Stats: 2235 lines in 19 files changed: 2 ins; 2211 del; 22 mod Patch: https://git.openjdk.org/jdk/pull/22861.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22861/head:pull/22861 PR: https://git.openjdk.org/jdk/pull/22861 From qxing at openjdk.org Tue Dec 24 03:26:24 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:26:24 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 18:57:39 GMT, Kim Barrett wrote: >> Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: >> >> - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). >> - Do not touch files in test. >> - Do not touch upstream data from CLDR. > > doc/hotspot-unit-tests.html line 248: > >> 246: so there is no need to have them in error messages. Asserts print only >> 247: compared values, they do not print any of interim variables, e.g. >> 248: ASSERT_TRUE(val1 == val2 && isFail(foo(8)) || i == 18) > > This file is generated from the .md file, and should not be edited directly. Updated both `.md` and `.html` using `make update-build-docs` in the latest commit. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896332803 From qxing at openjdk.org Tue Dec 24 03:26:24 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:26:24 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 17:11:14 GMT, Justin Lu wrote: >> Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: >> >> - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). >> - Do not touch files in test. >> - Do not touch upstream data from CLDR. > > make/data/cldr/common/main/kn.xml line 1085: > >> 1083: ????????? ?????????? >> 1084: ?????????-?????? ?????????? >> 1085: ?????????? ??????????? (???? ???????, ????????) > > Hi, we would not modify the contents of upstream data from CLDR. Sorry, I've reverted these changes in the latest commit. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896331971 From qxing at openjdk.org Tue Dec 24 03:26:24 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:26:24 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: Message-ID: <4QfTqVdt_-vwDpQQAaeiElZLvHDDBabcyBtISbLrmPo=.7aa033a5-d09b-4193-9d2e-1336167a10ce@github.com> On Mon, 23 Dec 2024 14:00:54 GMT, Erik Joelsson wrote: >> Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: >> >> - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). >> - Do not touch files in test. >> - Do not touch upstream data from CLDR. > > doc/hotspot-unit-tests.md line 175: > >> 173: there is no need to have them in error messages. Asserts print only >> 174: compared values, they do not print any of interim variables, e.g. >> 175: `ASSERT_TRUE(val1 == val2 && isFail(foo(8)) || i == 18)` prints only > > Looking at this expression, I believe the intention is this. > Suggestion: > > `ASSERT_TRUE((val1 == val2 && isFail(foo(8))) || i == 18)` prints only Thanks for the suggestion, updated. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896331528 From qxing at openjdk.org Tue Dec 24 03:32:36 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:32:36 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: Message-ID: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> On Mon, 23 Dec 2024 19:13:09 GMT, Kim Barrett wrote: >> Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: >> >> - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). >> - Do not touch files in test. >> - Do not touch upstream data from CLDR. > > test/hotspot/jtreg/testlibrary/ctw/Makefile line 50: > >> 48: $(TESTLIBRARY_DIR)/jdk/test/lib/util \ >> 49: $(TESTLIBRARY_DIR)/jtreg \ >> 50: -maxdepth 1 -name '*.java') > > I wonder why this hasn't caused problems and been found long ago? Does make just drop that stray > close-paren? I've tested this by running `make`, and the previous Makefile reports an error like file `test/lib/jtreg/SkippedException.java)` not found. So this fix is necessary. I also checked the git log, this change was introduced in https://github.com/openjdk/jdk/pull/22420, not that long ago. > test/jaxp/javax/xml/jaxp/unittest/transform/Bug8169112.xsl line 65: > >> 63: @page { margin: 0.1in; } >> 64: >> 65: } > > Does this affect the behavior of the test this is part of? Reverted. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896336118 PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896337303 From qxing at openjdk.org Tue Dec 24 03:35:47 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Tue, 24 Dec 2024 03:35:47 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: <_AIqmu61ZK3rRO-44sivWfkuH1ceJm8bQ3MtL2cu8vs=.f4c3bb3b-3697-4ba4-8199-0f1cf9f2f047@github.com> References: <_AIqmu61ZK3rRO-44sivWfkuH1ceJm8bQ3MtL2cu8vs=.f4c3bb3b-3697-4ba4-8199-0f1cf9f2f047@github.com> Message-ID: On Mon, 23 Dec 2024 22:16:01 GMT, Phil Race wrote: >> I was also wondering how this was tested. > > FYI, the way to test this is .. > cd test/jdk > jtreg sanity/client/SwingSet/src/TableDemoTest.java > > I tried converting all ^M to \n in this file another repo and comparing with your patch but every line was different so I just can't review this. For safety reasons I've restored this file as well as all the files in unit tests. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896338401 From erikj at openjdk.org Tue Dec 24 14:57:36 2024 From: erikj at openjdk.org (Erik Joelsson) Date: Tue, 24 Dec 2024 14:57:36 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> References: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> Message-ID: On Tue, 24 Dec 2024 03:26:23 GMT, Qizheng Xing wrote: >> This patch fixes unmatched brackets in some source files. > > Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: > > - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). > - Do not touch files in test. > - Do not touch upstream data from CLDR. I've reviewed doc/hotspot-unit-tests.* and the Makefile. ------------- Marked as reviewed by erikj (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22861#pullrequestreview-2522037503 From liach at openjdk.org Tue Dec 24 15:48:38 2024 From: liach at openjdk.org (Chen Liang) Date: Tue, 24 Dec 2024 15:48:38 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> References: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> Message-ID: On Tue, 24 Dec 2024 03:28:31 GMT, Qizheng Xing wrote: >> test/hotspot/jtreg/testlibrary/ctw/Makefile line 50: >> >>> 48: $(TESTLIBRARY_DIR)/jdk/test/lib/util \ >>> 49: $(TESTLIBRARY_DIR)/jtreg \ >>> 50: -maxdepth 1 -name '*.java') >> >> I wonder why this hasn't caused problems and been found long ago? Does make just drop that stray >> close-paren? > > I've tested this by running `make`, and the previous Makefile reports an error like file `test/lib/jtreg/SkippedException.java)` not found. So this fix is necessary. > > I also checked the git log, this change was introduced in https://github.com/openjdk/jdk/pull/22420, not that long ago. Hmm, apparently this is not run as part of tier 1-3, which I ran in my patch. I wonder how this test is run. And it means this patch needs to be backported to 24. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896838026 From liach at openjdk.org Tue Dec 24 15:48:37 2024 From: liach at openjdk.org (Chen Liang) Date: Tue, 24 Dec 2024 15:48:37 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> References: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> Message-ID: On Tue, 24 Dec 2024 03:26:23 GMT, Qizheng Xing wrote: >> This patch fixes unmatched brackets in some source files. > > Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: > > - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). > - Do not touch files in test. > - Do not touch upstream data from CLDR. Thanks for the ctw fix. ------------- Marked as reviewed by liach (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22861#pullrequestreview-2522077710 From kbarrett at openjdk.org Tue Dec 24 20:30:37 2024 From: kbarrett at openjdk.org (Kim Barrett) Date: Tue, 24 Dec 2024 20:30:37 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> Message-ID: On Tue, 24 Dec 2024 15:45:24 GMT, Chen Liang wrote: >> I've tested this by running `make`, and the previous Makefile reports an error like file `test/lib/jtreg/SkippedException.java)` not found. So this fix is necessary. >> >> I also checked the git log, this change was introduced in https://github.com/openjdk/jdk/pull/22420, not that long ago. > > Hmm, apparently this is not run as part of tier 1-3, which I ran in my patch. I wonder how this test is run. And it means this patch needs to be backported to 24. Only this small piece would be appropriate for backport to 24. I suggest splitting this out into its own bug, fixing it in isolation, and backporting that. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896952109 From kbarrett at openjdk.org Tue Dec 24 22:25:41 2024 From: kbarrett at openjdk.org (Kim Barrett) Date: Tue, 24 Dec 2024 22:25:41 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> Message-ID: On Tue, 24 Dec 2024 20:27:37 GMT, Kim Barrett wrote: >> Hmm, apparently this is not run as part of tier 1-3, which I ran in my patch. I wonder how this test is run. And it means this patch needs to be backported to 24. > > Only this small piece would be appropriate for backport to 24. I suggest splitting this out into its own bug, > fixing it in isolation, and backporting that. The purpose of this Makefile seems to be to build ctw.jar. So far as I can tell, nothing in the JDK uses that jar, or invokes that Makefile. There are some tests for the ctw component in hotspot/jtreg/testlibrary_tests/ctw. I think if you ran tier4 testing that you would hit those. Or you could use `TEST=hotspot:hotspot_misc`, or specify that directory. But those tests don't appear to use that jar. So I think there isn't a test that touches this Makefile. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1896981987 From kbarrett at openjdk.org Tue Dec 24 22:36:47 2024 From: kbarrett at openjdk.org (Kim Barrett) Date: Tue, 24 Dec 2024 22:36:47 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> References: <2MNSzuaI99GRQMqD4tbU5VMfHjwfm3KzzTBySopxKJM=.af677925-5588-456c-86c0-7bb262c2cec2@github.com> Message-ID: <5RJCjU8mibDWRUFIu_5QaivS78cZGFT1ECjS4_f2Z8E=.a8ff6fd5-cba0-40f5-b754-9bdb6f7e8d4b@github.com> On Tue, 24 Dec 2024 03:26:23 GMT, Qizheng Xing wrote: >> This patch fixes unmatched brackets in some source files. > > Qizheng Xing has updated the pull request incrementally with three additional commits since the last revision: > > - Update `hotspot-unit-tests.md` and HTML (using Pandoc 2.19.2). > - Do not touch files in test. > - Do not touch upstream data from CLDR. The fix for the ctw Makefile should not be included in this PR. It's a bug, and needs to be fixed separately and backported to 24 to fix the introduction there via the backport of JDK-8334733 from 25 to 24, without dragging the rest of this back to 24. ------------- Changes requested by kbarrett (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22861#pullrequestreview-2522228423 From lmesnik at openjdk.org Wed Dec 25 01:47:37 2024 From: lmesnik at openjdk.org (Leonid Mesnik) Date: Wed, 25 Dec 2024 01:47:37 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v2] In-Reply-To: References: <8pTor9oXFFHRouI1-vrAKdlTzPX9cHlU5s3RbqxBx34=.3b5db6b0-d8ee-4ac9-b29e-d3bbf21740d3@github.com> Message-ID: <7rkkA5WQNof4ipfVB0NnpXU1o_nHsPmW3rulRPp78ZU=.593fc62d-f6ae-4885-b6db-09822cfb45ef@github.com> On Tue, 24 Dec 2024 22:22:28 GMT, Kim Barrett wrote: >> Only this small piece would be appropriate for backport to 24. I suggest splitting this out into its own bug, >> fixing it in isolation, and backporting that. > > The purpose of this Makefile seems to be to build ctw.jar. So far as I can tell, nothing in the JDK uses that jar, > or invokes that Makefile. There are some tests for the ctw component in hotspot/jtreg/testlibrary_tests/ctw. I > think if you ran tier4 testing that you would hit those. Or you could use `TEST=hotspot:hotspot_misc`, or > specify that directory. But those tests don't appear to use that jar. So I think there isn't a test that touches > this Makefile. This makefile is not used by jtreg tests. The ctw code is compiled with `@library /test/lib / /testlibrary/ctw/src` so jtreg compiled the ctw library files itself. This makefile might be used for standalone build if needed. Thanks for fixing this! ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22861#discussion_r1897036236 From qxing at openjdk.org Wed Dec 25 02:34:16 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Wed, 25 Dec 2024 02:34:16 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v3] In-Reply-To: References: Message-ID: > This patch fixes unmatched brackets in some source files. Qizheng Xing has updated the pull request incrementally with one additional commit since the last revision: Revert fix in the CTW Makefile. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/22861/files - new: https://git.openjdk.org/jdk/pull/22861/files/ec3e6aa5..7f85c5e3 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=22861&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=22861&range=01-02 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/22861.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/22861/head:pull/22861 PR: https://git.openjdk.org/jdk/pull/22861 From qxing at openjdk.org Wed Dec 25 02:37:41 2024 From: qxing at openjdk.org (Qizheng Xing) Date: Wed, 25 Dec 2024 02:37:41 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v3] In-Reply-To: References: Message-ID: On Mon, 23 Dec 2024 19:42:34 GMT, Kim Barrett wrote: >> I strongly suggest avoiding omnibus changes like this when possible (which it >> is here). Just because it's all about one "kind" of change doesn't make it a >> cohesive change. This is touching many distinct areas of the JDK, and several >> different languages as well. 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 the whole thing might get stalled by discussion of one >> piece. >> >> There is also no mention of what testing has been done for this PR. Some of >> the changes are in executable code, and need to be tested. >> >> I think that all of the files in make/data/cldr/common are from the Unicode >> Consortium, and should not be modified here. > >> 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 right before Christmas. @kimbarrett @liach Thanks for your suggestions! I've moved the fix for the CTW Makefile to a separate pull request: https://github.com/openjdk/jdk/pull/22878, please check it. ------------- PR Comment: https://git.openjdk.org/jdk/pull/22861#issuecomment-2561558033 From kbarrett at openjdk.org Wed Dec 25 04:57:39 2024 From: kbarrett at openjdk.org (Kim Barrett) Date: Wed, 25 Dec 2024 04:57:39 GMT Subject: RFR: 8346773: Fix unmatched brackets in source files [v3] In-Reply-To: References: Message-ID: On Wed, 25 Dec 2024 02:34:16 GMT, Qizheng Xing wrote: >> This patch fixes unmatched brackets in some source files. > > Qizheng Xing has updated the pull request incrementally with one additional commit since the last revision: > > Revert fix in the CTW Makefile. Looks good. ------------- Marked as reviewed by kbarrett (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/22861#pullrequestreview-2522326924 From duke at openjdk.org Thu Dec 26 16:42:41 2024 From: duke at openjdk.org (Brett Okken) Date: Thu, 26 Dec 2024 16:42:41 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 20 Dec 2024 21:06:16 GMT, Naoto Sato wrote: >> The change made in [JDK-8288723](https://bugs.openjdk.org/browse/JDK-8288723) seems innocuous, but it caused this performance regression. Partially reverting the change (ones that involve `computeIfAbsent()`) to the original. Provided a benchmark that iterates the call to `ZoneOffset.ofTotalSeconds(0)` 1,000 times, which improves the operation time from 3,946ns to 2,241ns. > > Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: > > Fixed compile error src/java.base/share/classes/java/time/format/DateTimeTextProvider.java line 316: > 314: store = createStore(field, locale); > 315: CACHE.putIfAbsent(key, store); > 316: store = CACHE.get(key); should this be `store = CACHE.computeIfAbsent(key, e -> createStore(e.getKey(), e.getValue()));` That still allow the optimistic/concurrent get call to succeed most of the time (when already cached) but reduce the interactions with the map when a value is created/set/accessed the first time. Alternatively, the result of `putIfAbsent` could be checked/used to avoid the second call to `get`. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1898012555 From aturbanov at openjdk.org Thu Dec 26 17:28:35 2024 From: aturbanov at openjdk.org (Andrey Turbanov) Date: Thu, 26 Dec 2024 17:28:35 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Thu, 26 Dec 2024 16:39:58 GMT, Brett Okken wrote: >> Naoto Sato has updated the pull request incrementally with one additional commit since the last revision: >> >> Fixed compile error > > src/java.base/share/classes/java/time/format/DateTimeTextProvider.java line 316: > >> 314: store = createStore(field, locale); >> 315: CACHE.putIfAbsent(key, store); >> 316: store = CACHE.get(key); > > should this be > `store = CACHE.computeIfAbsent(key, e -> createStore(e.getKey(), e.getValue()));` > > That still allow the optimistic/concurrent get call to succeed most of the time (when already cached) but reduce the interactions with the map when a value is created/set/accessed the first time. > > Alternatively, the result of `putIfAbsent` could be checked/used to avoid the second call to `get`. For sure we should use result of `putIfAbsent`. Let's do this for all cases. See how it was implemented in my first commit - https://github.com/openjdk/jdk/pull/9208/commits/73a2f6cb1b91f4d7ee374089f35a72ef7b94433b ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1898031238 From duke at openjdk.org Thu Dec 26 19:42:45 2024 From: duke at openjdk.org (duke) Date: Thu, 26 Dec 2024 19:42:45 GMT Subject: =?utf-8?q?Withdrawn=3A_8335791=3A_Speed_=E2=80=8B?= =?utf-8?b?4oCLdXAgai51LkZvcm1hdHRlciAmIFN0cmluZy5mb3JtYXQ=?= In-Reply-To: References: Message-ID: <3UduOadS7bDdKdv4JdRzd4Wg0VosJwCGK47sEWt6K3c=.d4a3a18f-caf4-442e-9603-f85375385629@github.com> On Fri, 5 Jul 2024 15:40:24 GMT, Shaojin Wen wrote: > String.format is widely used, and improving its performance is very meaningful. This PR can significantly improve the performance of String.format. Sorry, there are many changes, which will take a lot of time. I hope you can review it patiently. > > > Improved performance includes the following: > > ## 1. Write directly during the parse process to reduce object allocation. > > In the current Formatter implementation, some objects do not need to be allocated, such as: > > > class Formatter { > public Formatter format(Locale l, String format, Object ... args) { > List fsa = parse(format); > // ... > } > > static List parse(String s) { > ArrayList al = new ArrayList<>(); > > while (i < max) { > int n = s.indexOf('%', i); > if (n < 0) { > // > al.add(new FixedString(s, i, max)); > } > } > } > } > > In the process of parsing, the content that is not a Specifier is directly appended without going through FixedString. By directly printing the parsed FormatString object, there is no need to construct a `List fsa` to store it. > > ## 2. Fast path print > Use specialized FormatString implementations for single-character and single-width specifiers to avoid calling the large FormatSpecifier#print method. > > ## 3. String.format directly calls j.u.Formatter > String.format directly calls j.u.Formatter via SharedSecrets to improve performance This pull request has been closed without being integrated. ------------- PR: https://git.openjdk.org/jdk/pull/20055 From duke at openjdk.org Thu Dec 26 19:43:48 2024 From: duke at openjdk.org (duke) Date: Thu, 26 Dec 2024 19:43:48 GMT Subject: Withdrawn: 8335366: Improve String.format performance with fastpath In-Reply-To: <7UuohcnXK5YTn1--FaQc0Pf6SA99Dau6PJWE6U9NjEk=.db32c5d6-d59d-40fe-85bc-e64223a2693c@github.com> References: <7UuohcnXK5YTn1--FaQc0Pf6SA99Dau6PJWE6U9NjEk=.db32c5d6-d59d-40fe-85bc-e64223a2693c@github.com> Message-ID: On Sat, 29 Jun 2024 11:53:31 GMT, Shaojin Wen wrote: > We need a String format solution with good performance. String Template was once expected, but it has been removed. j.u.Formatter is powerful, but its performance is not good enough. > > This PR implements a subset of j.u.Formatter capabilities. The performance is good enough that it is a fastpath for commonly used functions. When the supported functions are exceeded, it will fall back to using j.u.Formatter. > > The performance of this implementation is good enough, the fastpath has low detection cost, There is no noticeable performance degradation when falling back to j.u.Formatter via fastpath. > > Below is a comparison of String.format and concat-based and StringBuilder: > > * benchmark java code > > public class StringFormat { > @Benchmark > public String stringIntFormat() { > return "%s %d".formatted(s, i); > } > > @Benchmark > public String stringIntConcat() { > return s + " " + i; > } > > @Benchmark > public String stringIntStringBuilder() { > return new StringBuilder(s).append(" ").append(i).toString(); > } > } > > > * benchmark number on macbook m1 pro > > Benchmark Mode Cnt Score Error Units > StringFormat.stringIntConcat avgt 15 6.541 ? 0.056 ns/op > StringFormat.stringIntFormat avgt 15 17.399 ? 0.133 ns/op > StringFormat.stringIntStringBuilder avgt 15 8.004 ? 0.063 ns/op > > > From the above data, we can see that the implementation of fastpath reduces the performance difference between String.format and StringBuilder from 10 times to 2~3 times. > > The implementation of fastpath supports the following four specifiers, which can appear at most twice and support a width of 1 to 9. > > d > x > X > s > > If necessary, we can add a few more. > > > Below is a comparison of performance numbers running on a MacBook M1, showing a significant performance improvement. > > -Benchmark Mode Cnt Score Error Units (baseline) > -StringFormat.complexFormat avgt 15 895.954 ? 52.541 ns/op > -StringFormat.decimalFormat avgt 15 277.420 ? 18.254 ns/op > -StringFormat.stringFormat avgt 15 66.787 ? 2.715 ns/op > -StringFormat.stringIntFormat avgt 15 81.046 ? 1.879 ns/op > -StringFormat.widthStringFormat avgt 15 38.897 ? 0.114 ns/op > -StringFormat.widthStringIntFormat avgt 15 109.841 ? 1.028 ns/op > > +Benchmark Mode Cnt Score Error Units (current f925339e93fdf7a281462554ce5d73139bd0f0cd) > +StringFormat.complexF... This pull request has been closed without being integrated. ------------- PR: https://git.openjdk.org/jdk/pull/19956 From acobbs at openjdk.org Fri Dec 27 16:29:41 2024 From: acobbs at openjdk.org (Archie Cobbs) Date: Fri, 27 Dec 2024 16:29:41 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Thu, 26 Dec 2024 17:25:55 GMT, Andrey Turbanov wrote: > For sure we should use result of `putIfAbsent` Drive-by comment... >From what i can infer, the performance regression being addressed here is caused in part by the fact that (for example) `ConcurrentHashMap.computeIfAbsent()` provides an atomicity guarantee, which is a stronger requirement than is necessary here, and therefore by splitting up that call up into two separate, non-atomic `get()` and `put()` calls we get (counter-intuitively) faster execution time, even though there are more lines of code. Note `putIfAbsent()` also guarantees atomicity, so the same problem of slowness caused by "unnecessary atomicity" might occur with it as well. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1898609222 From liach at openjdk.org Fri Dec 27 23:27:39 2024 From: liach at openjdk.org (Chen Liang) Date: Fri, 27 Dec 2024 23:27:39 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 27 Dec 2024 16:27:10 GMT, Archie Cobbs wrote: >> For sure we should use result of `putIfAbsent`. Let's do this for all cases. See how it was implemented in my first commit - https://github.com/openjdk/jdk/pull/9208/commits/73a2f6cb1b91f4d7ee374089f35a72ef7b94433b > >> For sure we should use result of `putIfAbsent` > > Drive-by comment... > > From what i can infer, the performance regression being addressed here is caused in part by the fact that (for example) `ConcurrentHashMap.computeIfAbsent()` provides an atomicity guarantee, which is a stronger requirement than is necessary here, and therefore by splitting up that call up into two separate, non-atomic `get()` and `put()` calls we get (counter-intuitively) faster execution time, even though there are more lines of code. Note `putIfAbsent()` also guarantees atomicity, so the same problem of slowness caused by "unnecessary atomicity" might occur with it as well. Indeed, just noticed that both `computeIfAbsent` and `putIfAbsent` may acquire the lock when the key is present, while `get` never acquires a lock for read-only access. Maybe the implementation was written back when locking was less costly (with biased locking, etc.). Now we might have to reconsider locking until we know for sure a plain get fails. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1898748424 From jwaters at openjdk.org Mon Dec 30 13:46:35 2024 From: jwaters at openjdk.org (Julian Waters) Date: Mon, 30 Dec 2024 13:46:35 GMT Subject: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] In-Reply-To: References: Message-ID: On Thu, 31 Oct 2024 05:43:11 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 unused warnings and addressed all of them by commenting out the code as appropriate. I am confident that in many cases this simplistic approach of commenting out code does not fix the underlying issue, and the warning actually found a bug that should be fixed. In these instances, I will be aiming to fix these bugs with help from reviewers, so I recommend anyone reviewing who knows more about the code than I do to see whether there is indeed a bug that needs fixing in a different way than what I did > > Julian Waters has updated the pull request incrementally with one additional commit since the last revision: > > Remove the got local Stop asking, I still need awt and accessibility to be approved :( ------------- PR Comment: https://git.openjdk.org/jdk/pull/21654#issuecomment-2565503212 From duke at openjdk.org Mon Dec 30 17:46:37 2024 From: duke at openjdk.org (Brett Okken) Date: Mon, 30 Dec 2024 17:46:37 GMT Subject: RFR: 8345668: ZoneOffset.ofTotalSeconds performance regression [v3] In-Reply-To: References: Message-ID: On Fri, 27 Dec 2024 23:24:46 GMT, Chen Liang wrote: >>> For sure we should use result of `putIfAbsent` >> >> Drive-by comment... >> >> From what i can infer, the performance regression being addressed here is caused in part by the fact that (for example) `ConcurrentHashMap.computeIfAbsent()` provides an atomicity guarantee, which is a stronger requirement than is necessary here, and therefore by splitting up that call up into two separate, non-atomic `get()` and `put()` calls we get (counter-intuitively) faster execution time, even though there are more lines of code. Note `putIfAbsent()` also guarantees atomicity, so the same problem of slowness caused by "unnecessary atomicity" might occur with it as well. > > Indeed, just noticed that both `computeIfAbsent` and `putIfAbsent` may acquire the lock when the key is present, while `get` never acquires a lock for read-only access. > > Maybe the implementation was written back when locking was less costly (with biased locking, etc.). Now we might have to reconsider locking until we know for sure a plain get fails. This scenario is discussed in Effective Java by Joshua Block. His observation then (java 5/6 time frame?) was optimistically calling `get` first and only calling `putIfAbsent` or `computeIfAbsent` if the `get` returned `null` was 250% faster, and this is because calls to put/compute ifAbsent have contention. There have been changes made to those methods since then to try to avoid synchronization when the key is already present, but the observation seems to confirm that the optimistic `get` call first is still faster (though a much smaller difference). My comment was not to revert back to the prior change of just calling `computeIfAbsent`, but rather just to change the (expected rare) case when the first `get` returns `null` to replace the `putIfAbsent` and second `get` call with a single `computeIfAbsent` (or utilize the result of `putIfAbsent` to avoid the second call to `get`). ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/22854#discussion_r1899699668