8268482: compiler/intrinsics/VectorizedMismatchTest.java failed with failed: length in range

[jatin-bhateja]

Problem was reported on a virtualized HW which was enabled with non-standard options.
As a safety check postponing the vector type creation un-till HW features needed for partial in-lining are checked.

---

Progress

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

Issue

• JDK-8268482: compiler/intrinsics/VectorizedMismatchTest.java failed with failed: length in range

Reviewers

• Vladimir Ivanov (@iwanowww - Reviewer)
• Nils Eliasson (@neliasso - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 125

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

Using diff file

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

[jatin-bhateja]

/label hotspot-compiler-dev

[bridgekeeper]

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

@jatin-bhateja
The hotspot-compiler label was successfully added.

[mlbridge]

Webrevs

• 00: Full (29e4d119)

[iwanowww]

Looks good.

[openjdk]

@jatin-bhateja 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:

8268482: compiler/intrinsics/VectorizedMismatchTest.java failed with failed: length in range

Reviewed-by: vlivanov, neliasso

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

• 1b2147a: 8269125: Klass enqueue element size calculation wrong when traceid value cross compress limit
• bf70620: 8268961: Parenthesized pattern with guards does not work
• 8128ca1: 8269066: assert(ZAddress::is_marked(addr)) failed: Should be marked

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[neliasso]

Looks good.

[jatin-bhateja]

/integrate

[openjdk]

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

• a30141d: 8269179: Crash in TestMacroLogicVector::testSubWordBoolean: assert(_base >= VectorMask && _base <= VectorZ) failed: Not a Vector
• b474314: 8266854: LibraryCallKit::inline_preconditions_checkIndex modifies control flow even if the intrinsic bailed out
• 7e96318: 8254571: Erroneous generic type inference in a lambda expression with a checked exception
• 1b2147a: 8269125: Klass enqueue element size calculation wrong when traceid value cross compress limit
• bf70620: 8268961: Parenthesized pattern with guards does not work
• 8128ca1: 8269066: assert(ZAddress::is_marked(addr)) failed: Should be marked

Your commit was automatically rebased without conflicts.

[openjdk]

@jatin-bhateja Pushed as commit 0c3fc27.

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