Skip to content

8283740: C1: Convert flag TwoOperandLIRForm to a constant on all platforms #11671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

dafedafe
Copy link
Contributor

@dafedafe dafedafe commented Dec 14, 2022

The TwoOperandLIRForm flag (LIR requires src1 and dst to match in binary LIR ops) can be set at runtime but each platform defines a default value that is the only one accepted. Although some platform could theoretically support both, there is no realistic scenario for this.
The flag is removed in favour of a constant. This is defined as enum and its assigned value is defined in the platform-specific def.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8283740: C1: Convert flag TwoOperandLIRForm to a constant on all platforms

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11671/head:pull/11671
$ git checkout pull/11671

Update a local copy of the PR:
$ git checkout pull/11671
$ git pull https://git.openjdk.org/jdk pull/11671/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 11671

View PR using the GUI difftool:
$ git pr show -t 11671

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11671.diff

@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Dec 14, 2022
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 14, 2022

Hi @dafedafe, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user dafedafe" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Dec 14, 2022

@dafedafe The following labels will be automatically applied to this pull request:

  • hotspot
  • shenandoah

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added hotspot hotspot-dev@openjdk.org shenandoah shenandoah-dev@openjdk.org labels Dec 14, 2022
@dafedafe dafedafe marked this pull request as ready for review December 14, 2022 12:59
Copy link
Member

@TobiHartmann TobiHartmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks good to me but I think all these platform dependent constants should be converted to static const declarations at some point. From what I understand, enums are used here only for historical reasons. Could you file a follow-up RFE to investigate?

Copy link
Member

@chhagedorn chhagedorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks good to me!

That looks good to me but I think all these platform dependent constants should be converted to static const declarations at some point. From what I understand, enums are used here only for historical reasons. Could you file a follow-up RFE to investigate?

That's a good idea to clean this up as well at some point. But probably too much for this PR. So, I agree to file a separate RFE for it.

@dafedafe
Copy link
Contributor Author

/label remove shenandoah

@openjdk openjdk bot removed the shenandoah shenandoah-dev@openjdk.org label Dec 14, 2022
@openjdk
Copy link

openjdk bot commented Dec 14, 2022

@dafedafe
The shenandoah label was successfully removed.

@TobiHartmann
Copy link
Member

And FTR:

Due to bugs in certain (very old) compilers, there is widespread use of enums and avoidance of in-class initialization of static integral constant members. Compilers having such bugs are no longer supported. Except where an enum is semantically appropriate, new code should use integral constants.

https://github.com/openjdk/jdk/blob/master/doc/hotspot-style.md

@bridgekeeper bridgekeeper bot removed the oca Needs verification of OCA signatory status label Dec 16, 2022
@openjdk
Copy link

openjdk bot commented Dec 16, 2022

@dafedafe This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8283740: C1: Convert flag TwoOperandLIRForm to a constant on all platforms

Reviewed-by: thartmann, chagedorn

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 70 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TobiHartmann, @chhagedorn) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added ready Pull request is ready to be integrated rfr Pull request is ready for review labels Dec 16, 2022
@mlbridge
Copy link

mlbridge bot commented Dec 16, 2022

Webrevs

@dafedafe
Copy link
Contributor Author

@TobiHartmann @chhagedorn thanks for the review!

@dafedafe
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Dec 19, 2022
@openjdk
Copy link

openjdk bot commented Dec 19, 2022

@dafedafe
Your change (at version cdfd2b1) is now ready to be sponsored by a Committer.

@TobiHartmann
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Dec 19, 2022

Going to push as commit 86d588b.
Since your change was applied there have been 71 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Dec 19, 2022
@openjdk openjdk bot closed this Dec 19, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Dec 19, 2022
@openjdk
Copy link

openjdk bot commented Dec 19, 2022

@TobiHartmann @dafedafe Pushed as commit 86d588b.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants