Details
-
Bug
-
Resolution: Fixed
-
P4
-
11.0.22, 17.0.9, 21.0.1, 22, 23
-
b08
-
generic
-
generic
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8326068 | 22.0.1 | Sergey Bylokhov | P4 | Resolved | Fixed | b05 |
JDK-8326072 | 21.0.3 | Sergey Bylokhov | P4 | Resolved | Fixed | b04 |
JDK-8326095 | 17.0.11 | Sergey Bylokhov | P4 | Resolved | Fixed | b04 |
JDK-8326098 | 11.0.23 | Sergey Bylokhov | P4 | Resolved | Fixed | b04 |
Description
https://gitlab.freedesktop.org/freetype/freetype/-/issues/1245
So now we can revert the workaround in the JDK:
https://bugs.openjdk.org/browse/JDK-8313576
Attachments
Issue Links
- backported by
-
JDK-8326068 Enable "maybe-uninitialized" warning for FreeType 2.13.1
- Resolved
-
JDK-8326072 Enable "maybe-uninitialized" warning for FreeType 2.13.1
- Resolved
-
JDK-8326095 Enable "maybe-uninitialized" warning for FreeType 2.13.1
- Resolved
-
JDK-8326098 Enable "maybe-uninitialized" warning for FreeType 2.13.1
- Resolved
- relates to
-
JDK-8316028 Update FreeType to 2.13.2
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/8af22e79
-
Commit openjdk/jdk17u-dev/ed7c6f4e
-
Commit openjdk/jdk21u-dev/70fa49ed
-
Commit openjdk/jdk22u/ab431cf9
-
Commit openjdk/jdk/781f368d
-
Review openjdk/jdk11u-dev/2499
-
Review openjdk/jdk17u-dev/2184
-
Review openjdk/jdk21u-dev/222
-
Review openjdk/jdk22u/51
-
Review openjdk/jdk/17525