8273263: Incorrect recovery attribution of record component type when j.l.Record is unavailable

[lahodaj]

This is a little obscure case where j.l.Record is not available, yet the source code contains a record, the AST model is slightly broken - the first record's component has an erroneous type. The reason is that syms.recordType is used directly, and when it is completed (for the first time), the CompletionFailure thrown will break the component's type. It would be better to report the error on the proper place at a proper place. This is already done for enums, where the supertype is attributed from an AST, which reports any errors at an appropriate place. The proposal in this patch is to also create a temporary AST for j.l.Record and attribute it, so that the errors are reported at an appropriate time and place.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8273263: Incorrect recovery attribution of record component type when j.l.Record is unavailable

Reviewers

• Vicente Romero (@vicente-romero-oracle - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5349/head:pull/5349
$ git checkout pull/5349

Update a local copy of the PR:
$ git checkout pull/5349
$ git pull https://git.openjdk.java.net/jdk pull/5349/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 5349

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5349.diff

[bridgekeeper]

👋 Welcome back jlahoda! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@lahodaj The following label will be automatically applied to this pull request:

• compiler

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.

[mlbridge]

Webrevs

• 00: Full (662c7e60)

[vicente-romero-oracle]

looks good

[openjdk]

@lahodaj 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:

8273263: Incorrect recovery attribution of record component type when j.l.Record is unavailable

Reviewed-by: vromero

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

• aaa6f69: 8273250: Address javadoc issues in Deflater::setDictionationary
• 5ee5dd9: 8272914: Create hotspot:tier2 and hotspot:tier3 test groups
• 5245c1c: 8273147: Update and restructure TestGCLogMessages log message list
• 632a7e0: 8273165: GraphKit::combine_exception_states fails with "matching stack sizes" assert
• c2e015c: 8273229: Update OS detection code to recognize Windows Server 2022
• 0c1b16b: 8273243: Fix indentations in java.net.InetAddress methods
• 152e669: 8273140: Replace usages of Enum.class.getEnumConstants() with Enum.values() where possible
• 857a930: 8263375: Support stack watermarks in Zero VM
• 6cfe314: 8272970: Parallelize runtime/InvocationTests/
• a9a83b2: 8273256: runtime/cds/appcds/TestEpsilonGCWithCDS.java fails due to Unrecognized VM option 'ObjectAlignmentInBytes=64' on x86_32
• ... and 229 more: https://git.openjdk.java.net/jdk/compare/a86ac0d1e3a6f02e587362c767abdf62b308d321...master

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 master branch, type /integrate in a new comment.

[lahodaj]

/integrate

[openjdk]

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

• fa9c865: 8273112: -Xloggc: should override -verbose:gc
• dd87181: 8214761: Bug in parallel Kahan summation implementation
• 7fff22a: 8272805: Avoid looking up standard charsets
• 92b05fe: 8273251: Call check_possible_safepoint() from SafepointMechanism::process_if_requested()
• 29e0f13: 8272385: Enforce ECPrivateKey d value to be in the range [1, n-1] for SunEC provider
• aaa6f69: 8273250: Address javadoc issues in Deflater::setDictionationary
• 5ee5dd9: 8272914: Create hotspot:tier2 and hotspot:tier3 test groups
• 5245c1c: 8273147: Update and restructure TestGCLogMessages log message list
• 632a7e0: 8273165: GraphKit::combine_exception_states fails with "matching stack sizes" assert
• c2e015c: 8273229: Update OS detection code to recognize Windows Server 2022
• ... and 234 more: https://git.openjdk.java.net/jdk/compare/a86ac0d1e3a6f02e587362c767abdf62b308d321...master

Your commit was automatically rebased without conflicts.

[openjdk]

@lahodaj Pushed as commit f17ee0c.

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