Profiling and repeat support for JVM CLI Compiler

compiler/testData/cli/jvm/extraHelp.out

@@ -74,6 +74,12 @@ where advanced options include:
   -Xno-param-assertions      Don't generate not-null assertions on parameters of methods accessible from Java
   -Xno-receiver-assertions   Don't generate not-null assertion for extension receiver arguments of platform types
   -Xno-use-ir                Do not use the IR backend. Useful for a custom-built compiler where IR backend is enabled by default
+  -Xprofile=<profilerPath:command:outputDir>
+                             Debug option: Run compiler with async profiler, save snapshots to outputDir, command is passed to async-profiler on start
+                             You'll have to provide async-profiler.jar on classpath to use this
+                             profilerPath is a path to libasyncProfiler.so
+                             Example: -Xprofile=<PATH_TO_ASYNC_PROFILER>/async-profiler/build/libasyncProfiler.so:event=cpu,interval=1ms,threads,start,framebuf=50000000:<SNAPSHOT_DIR_PATH>
+  -Xrepeat=<number>          Debug option: Repeats modules compilation <number> times
   -Xsanitize-parentheses     Transform '(' and ')' in method names to some other character sequence.
                              This mode can BREAK BINARY COMPATIBILITY and is only supposed to be used to workaround
                              problems with parentheses in identifiers on certain platforms