-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8310405: Linker.Option.firstVariadicArg should specify which index values are valid #14565
Conversation
👋 Welcome back jvernee! A progress list of the required criteria for merging this PR into |
@JornVernee The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
* | ||
* @param index the index of the first variadic argument layout in the function descriptor associated | ||
* with a downcall linkage request. | ||
* @param index the index indicating the start of the variadic arguments passed to the function described by |
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.
My general feeling is that the previous text was better here. We describe in plenty details what this "index" is in the method javadoc. I think I'm more for reverting the changes here.
Co-authored-by: Maurizio Cimadamore <54672762+mcimadamore@users.noreply.github.com>
I've addressed the review comments. I think we're converging so also went ahead and created the CSR for this. |
/csr unneeded |
@JornVernee determined that a CSR request is not needed for this pull request. |
@JornVernee 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:
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 120 new commits pushed to the
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. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 7fffdb5.
Your commit was automatically rebased without conflicts. |
@JornVernee Pushed as commit 7fffdb5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk21 |
@JornVernee the backport was successfully created on the branch JornVernee-backport-7fffdb5e in my personal fork of openjdk/jdk21. To create a pull request with this backport targeting openjdk/jdk21:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk21:
|
Improve the specification of
Linker.Option.firstVariadicArg
, by specifying more clearly which index values are valid.Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14565/head:pull/14565
$ git checkout pull/14565
Update a local copy of the PR:
$ git checkout pull/14565
$ git pull https://git.openjdk.org/jdk.git pull/14565/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14565
View PR using the GUI difftool:
$ git pr show -t 14565
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14565.diff
Webrev
Link to Webrev Comment