8260632: Build failures after JDK-8253353 #138
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine and trivial to me.
..Thomas
@shipilev This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good. I approved fix request for JDK 16.
Thank you. /integrate |
@shipilev Since your change was applied there has been 1 commit pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit bc41bb1. |
JDK-8253353 changed the field to
uint16_t
, and nowshenadoahSupport.cpp
code runs into ambiguity choosing betweenuint8_t
anduint16_t
when instantiatingMAX2
macro:Additional testing:
hotspot_gc_shenandoah
tier1
with ShenandoahProgress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk16 pull/138/head:pull/138
$ git checkout pull/138