-
Enhancement
-
Resolution: Fixed
-
P4
-
8, 11, 13
-
b05
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8260350 | 13.0.7 | Yuri Nesterenko | P4 | Resolved | Fixed | b01 |
JDK-8261054 | 13.0.6 | Yuri Nesterenko | P4 | Resolved | Fixed | b01 |
JDK-8252115 | 11.0.9 | Roman Kennke | P4 | Resolved | Fixed | b05 |
JDK-8252554 | openjdk8u272 | Roman Kennke | P4 | Resolved | Fixed | b06 |
Recent gcc (I use version 9) complains about using memset to initialize fields of decode_env. Let's use proper field initializers instead.
- backported by
-
JDK-8252115 Don't use memset to initialize fields decode_env constructor in disassembler.cpp
- Resolved
-
JDK-8252554 Don't use memset to initialize fields decode_env constructor in disassembler.cpp
- Resolved
-
JDK-8260350 Don't use memset to initialize fields decode_env constructor in disassembler.cpp
- Resolved
-
JDK-8261054 Don't use memset to initialize fields decode_env constructor in disassembler.cpp
- Resolved
- relates to
-
JDK-8259583 Remove unused decode_env::_codeBuffer
- Resolved
-
JDK-8252573 8u: Windows build failed after 8222079 backport
- Closed
(1 relates to, 2 links to)