Tobias Hartmann

I can run this through our testing but please resolve the merge conflict first.

Thanks, I can see failures with the following tests when running with `-XX:+UseCMoveUnconditionally -XX:+UseVectorCmov`: - `compiler/c2/TestCondAddDeadBranch.java` - `compiler/loopopts/TestCastFFAtPhi.java` ``` Error mixing types: vectory[4]:{double_top} and double_top ``` ``` # A fatal...

Okay, please go ahead and file a follow-up bug then.

/reviewers 2

I executed some quick testing and this fails with: ``` [2022-10-21T09:54:28,696Z] # A fatal error has been detected by the Java Runtime Environment: [2022-10-21T09:54:28,696Z] # [2022-10-21T09:54:28,696Z] # Internal Error (/opt/mach5/mesos/work_dir/slaves/0c72054a-24ab-4dbb-944f-97f9341a1b96-S8380/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/5903b026-cdbd-4aa4-8433-6a45fb7ee593/runs/f75b29aa-40ef-46a5-b323-3a80aaa9aa6b/workspace/open/src/hotspot/cpu/x86/assembler_x86.cpp:5358),...

Thanks, I'll re-run testing.

/reviewers 2

With your fix, correctness still depends on the order in which nodes are processed by IGVN, right? Wouldn't this still reproduce with `-XX:+StressIGVN`?

I just checked and I can still reproduce the issue with your fix. Simply run: `java -Xbatch -XX:CompileCommand=compileonly,Test::test -XX:+StressIGVN -XX:RepeatCompilation=10000 Test` So the root cause must be something else.

Comment to keep this open. @kelthuzadx, let me know if you need help with reproducing this.