Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: 24
Affects Version/s: 24
Component/s: hotspot
Labels:

Subcomponent:
compiler
Resolved In Build:
b24
CPU:

ppc

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8344406	21.0.6	Martin Doerr	P4	Resolved	Fixed	b04
JDK-8346371	17.0.15	Martin Doerr	P4	Resolved	Fixed	b01

The JVM currently allows switching on -XX:+OptoScheduling.
This should not be allowed because the required information in ppc.ad file is neither accurate nor complete.
~~JDK-8338446~~ shows that it implies Undefined Behavior.
We could implement support for OptoScheduling in the future, but the benefit is questionable because modern Power processors use out-of-order scheduling.

backported by

JDK-8344406 [PPC64] Disallow OptoScheduling

Resolved

JDK-8346371 [PPC64] Disallow OptoScheduling

Resolved

duplicates

JDK-8338446 UBSan: ad_ppc.hpp:4276:11: runtime error: shift exponent 100 is too large for 32-bit type 'unsigned int'

Closed

is cloned by

JDK-8343884 [s390x] Disallow OptoScheduling

Resolved

links to

Commit(master) openjdk/jdk17u-dev/0254b70a

Commit(master) openjdk/jdk21u-dev/38f654ee

Commit(master) openjdk/jdk/f621f26c

Review(master) openjdk/jdk17u-dev/3105

Review(master) openjdk/jdk21u-dev/1153

Review(master) openjdk/jdk/21935

(5 links to)

Assignee:: Martin Doerr

Reporter:: Martin Doerr

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024-11-06 08:10

Updated:: 2024-12-17 02:01

Resolved:: 2024-11-07 14:13

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates