You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To specify options in a subset (that apply only to some methods) you use the following format: -Xjit:{methodRegex}(options_in_subset)
On Linux this runs into the following error caused by the shell:
-bash: syntax error near unexpected token `('
Possible workarounds are:
Surround JIT command line options with single or double quotes
Escape the brackets: \(\)
However, when testing uses multiple levels of perl/python/shell scripts it becomes difficult to reason about what workarounds work.
This issue proposes the usage of square brackets for specifying options_in_subset, in addition to the round brackets. Thus, both -Xjit:{methodRegex}(options_in_subset)
and -Xjit:{methodRegex}[options_in_subset]
should be valid.
The text was updated successfully, but these errors were encountered:
This commit allows the user to specify options in a subset using
square brackets as opposed to normal brackets which is the norm.
E.g.: -Xjit:{methodRegex}[options-to-use]
Normal (round) brackets will continue to work as before.
Issue: eclipse-omr#7257
Signed-off-by: Marius Pirvu <[email protected]>
To specify options in a subset (that apply only to some methods) you use the following format:
-Xjit:{methodRegex}(options_in_subset)
On Linux this runs into the following error caused by the shell:
Possible workarounds are:
\(
\)
However, when testing uses multiple levels of perl/python/shell scripts it becomes difficult to reason about what workarounds work.
This issue proposes the usage of square brackets for specifying options_in_subset, in addition to the round brackets. Thus, both
-Xjit:{methodRegex}(options_in_subset)
and
-Xjit:{methodRegex}[options_in_subset]
should be valid.
The text was updated successfully, but these errors were encountered: