8332032: C2: Remove ExpandSubTypeCheckAtParseTime flag

[xiaotaonan]

C2: Remove ExpandSubTypeCheckAtParseTime flag

---

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-8332032: C2: Remove ExpandSubTypeCheckAtParseTime flag (Enhancement - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 19205

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back xiaotaonan! 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]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

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

• hotspot-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 (6491eb13)

[xiaotaonan]

@lgxbslgx

[xiaotaonan]

/signed

[bridgekeeper]

You are already a known contributor!

[chhagedorn]

Hi @xiaotaonan, please first ask in JBS if you can take over RFEs/bugs that are already assigned like this one, especially if it has just been filed. This PR misses the entire context why this flag should be removed and what the pros/cons and trade-offs are. I planned to do some more offline discussions first before proposing the actual PR to remove this flag since it is now related to an otherwise hard-to-fix bug in Valhalla.

[xiaotaonan]

please first ask in JBS if you can take over RFEs/bugs that are already assigned like this one, especially if it has just been filed. This PR misses the entire context why this flag should be removed and what the pros/cons and trade-offs are. I planned to do some more offline discussions first before proposing the actual PR to remove this flag since it is now related to an otherwise hard-to-fix bug in Valhalla.

OK.

[lgxbslgx]

@lgxbslgx

The reviewers (maybe me) of the corresponding area will review your patch. So I don't think you need to CC me especially.

[chhagedorn]

please first ask in JBS if you can take over RFEs/bugs that are already assigned like this one, especially if it has just been filed. This PR misses the entire context why this flag should be removed and what the pros/cons and trade-offs are. I planned to do some more offline discussions first before proposing the actual PR to remove this flag since it is now related to an otherwise hard-to-fix bug in Valhalla.

OK.

Thanks for your understanding and letting me taking this PR over - I will propose this change again later this week (we first also need to update some internal stress jobs that use this flag).