Eliminate the effect -Xaggressive has on switching to profiling

[mpirvu]

The option -Xaggressive allows switching to profiling of hot compilations
in a more aggressive manner. This has been seen to have negative performance
effects on some applications.
This commit eliminates the effect -Xaggressive has on switching to profiling.
More aggressive switching to profiling can be enabled with the newly created
option -Xjit:aggressiveSwitchingToProfiling

Another change is the elimination of code that tried to disable downgrading
to cold optimization level. That code had no effect because it was conditional
on an option that was not yet set at that point.

Depends on eclipse-omr/omr#6350

Signed-off-by: Marius Pirvu mpirvu@ca.ibm.com

[mpirvu]

FYI @vijaysun-omr

[mpirvu]

Converted to draft mode until the OMR change it depends on gets merged.

[vijaysun-omr]

Typo in commit message and PR abstract : "profilig"

[mpirvu]

Fixed the typo.

[vijaysun-omr]

Jenkins test extended all jdk11

[mpirvu]

One test on AIX failed, but from the error message, the failure doesn't seem connected to this PR

Running test testRASAPI_0 .
...
      [test]     [junit] ------------- Standard Output ---------------
     [test]     [junit] com.ibm.jvm.InvalidDumpOptionException: Error in dump options.
     [test]     [junit] reach here
     [test]     [junit] ------------- ---------------- ---------------
     [test]     [junit] 
     [test]     [junit] Testcase: testJavaDumpNoArgs took 0.04 sec
     [test]     [junit] Testcase: testJavaDumpWithFile took 0.034 sec
     [test]     [junit] Testcase: testJavaDumpWithOptions took 0.003 sec
     [test]     [junit] Testcase: testJavaDumpNullFile took 0.032 sec
     [test]     [junit] Testcase: testJavaDumpEmptyFile took 0.025 sec
     [test]     [junit] Testcase: testJavaDumpToDashFile took 0.494 sec
     [test]     [junit] Testcase: testJavaDumpWithSameFile took 1.069 sec
     [test]     [junit] Testcase: testHeapDumpNoArgs took 0.045 sec
     [test]     [junit] Testcase: testHeapDumpWithFile took 0.046 sec
     [test]     [junit] Testcase: testHeapDumpWithOptions took 0.002 sec
     [test]     [junit] Testcase: testHeapDumpNullFile took 0.045 sec
     [test]     [junit] Testcase: testHeapDumpToDashFile took 0.008 sec
     [test]     [junit] Testcase: testHeapDumpWithSameFile took 1.121 sec
     [test]     [junit] Testcase: testSnapDumpNoArgs took 0.106 sec
     [test]     [junit] Testcase: testSnapDumpWithFile took 0.11 sec
     [test]     [junit] Testcase: testSnapDumpWithOptions took 0.004 sec
     [test]     [junit] Testcase: testSnapDumpNullFile took 0.138 sec
     [test]     [junit] Testcase: testSnapDumpToDashFile took 0.009 sec
     [test]     [junit] Testcase: testSnapDumpWithSameFile took 1.232 sec
     [test]     [junit] Testcase: testSystemDumpNoArgs took 34.145 sec
     [test]     [junit] Testcase: testSystemDumpWithFile took 45.75 sec
     [test]     [junit] Testcase: testSystemDumpWithOptions took 0.643 sec
     [test]     [junit] Testcase: testSystemDumpNullFile took 146.664 sec
     [test]     [junit] 	Caused an ERROR
     [test]     [junit] Java heap space
     [test]     [junit] java.lang.OutOfMemoryError: Java heap space
     [test]     [junit] 	at java.base/java.lang.StringCoding.decodeUTF8_0(StringCoding.java:766)
     [test]     [junit] 	at java.base/java.lang.StringCoding.decodeUTF8(StringCoding.java:725)
     [test]     [junit] 	at java.base/java.lang.StringCoding.decode(StringCoding.java:237)
     [test]     [junit] 	at java.base/java.lang.String.<init>(String.java:602)
...

[pshipton]

The AIX failure is a known issue #14193

[mpirvu]

Based on Peter's comment, this PR is ready to be merged.