[OpenJDK 2D-Dev] Project Lanai (New Metal Java 2D Rendering pipeline for macOS) EA build 10 has been released

2021-03-03 Thread Philip Race
All, We have prepared an EA 10 build of Project Lanai for JEP 382 [1] incorporating fixes to feed back during the ongoing code review [2] EA 10 can be downloaded from https://jdk.java.net/lanai/. Note the open issues and testing suggestions given there. Please test with your apps and hardware

[OpenJDK 2D-Dev] Integrated: 8262915: java.awt.color.ColorSpace.getName() is not thread-safe

2021-03-03 Thread Sergey Bylokhov
On Wed, 3 Mar 2021 03:46:59 GMT, Sergey Bylokhov wrote: > The java.awt.color.ColorSpace.getName() method does not use any kind of > synchronization to properly initialize and use the static cache for the color > components names. This pull request has now been integrated. Changeset: b397472e

Re: [OpenJDK 2D-Dev] RFR: 8262915: java.awt.color.ColorSpace.getName() is not thread-safe

2021-03-03 Thread Sergey Bylokhov
On Wed, 3 Mar 2021 19:44:33 GMT, Alexander Zvegintsev wrote: >> src/java.desktop/share/classes/java/awt/color/ColorSpace.java line 454: >> >>> 452: * Returns the name of the component given the component index. >>> 453: * >>> 454: * @param component the component index >> >> Al

Re: [OpenJDK 2D-Dev] RFR: 8262915: java.awt.color.ColorSpace.getName() is not thread-safe

2021-03-03 Thread Alexey Ivanov
On Wed, 3 Mar 2021 03:46:59 GMT, Sergey Bylokhov wrote: > The java.awt.color.ColorSpace.getName() method does not use any kind of > synchronization to properly initialize and use the static cache for the color > components names. Marked as reviewed by aivanov (Reviewer). - PR: h

Re: [OpenJDK 2D-Dev] RFR: 8262915: java.awt.color.ColorSpace.getName() is not thread-safe

2021-03-03 Thread Alexander Zvegintsev
On Wed, 3 Mar 2021 03:55:42 GMT, Sergey Bylokhov wrote: >> The java.awt.color.ColorSpace.getName() method does not use any kind of >> synchronization to properly initialize and use the static cache for the >> color components names. > > src/java.desktop/share/classes/java/awt/color/ColorSpace.

Re: [OpenJDK 2D-Dev] RFR: 8262915: java.awt.color.ColorSpace.getName() is not thread-safe

2021-03-03 Thread Alexander Zvegintsev
On Wed, 3 Mar 2021 03:46:59 GMT, Sergey Bylokhov wrote: > The java.awt.color.ColorSpace.getName() method does not use any kind of > synchronization to properly initialize and use the static cache for the color > components names. Marked as reviewed by azvegint (Reviewer). - PR:

Re: [OpenJDK 2D-Dev] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port [v9]

2021-03-03 Thread Anton Kozlov
On Wed, 3 Mar 2021 17:46:41 GMT, Andrew Haley wrote: > A list of the bugs that our internal testing revealed so far ... Thank you! Some of them look like test issues, but a few need more serious consideration. I want to resolve https://bugs.openjdk.java.net/browse/JDK-8262903 at least, along w

Re: [OpenJDK 2D-Dev] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port [v9]

2021-03-03 Thread Andrew Haley
On Wed, 3 Mar 2021 17:39:28 GMT, Gerard Ziemski wrote: > A list of the bugs that our internal testing revealed so far: Are any of these blockers for integration? Some of them are to do with things like features that aren't yet supported, and we can't fix what we can't see. - PR: h

Re: [OpenJDK 2D-Dev] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port [v9]

2021-03-03 Thread Gerard Ziemski
On Tue, 2 Mar 2021 11:05:20 GMT, Anton Kozlov wrote: >> For platform files that were copied from other ports to this port, if the >> file wasn't >> changed I presume the copyright years are left alone. If the file required >> changes >> for this port, I expect the year to be updated to 2021. Ho

Re: [OpenJDK 2D-Dev] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port [v23]

2021-03-03 Thread Gerard Ziemski
On Tue, 2 Mar 2021 23:21:28 GMT, David Holmes wrote: > Note that `thread` can be NULL here if the signal handler is running in a > non-attached thread. If we then perform: > `ThreadWXEnable(WXMode new_mode, Thread* thread = NULL) : _thread(thread ? > thread : Thread::current()),` > we call Thre