RFR(S): 8247732: validate user-input intrinsic_ids in ControlIntrinsic
Tobias Hartmann
tobias.hartmann at oracle.com
Fri Jul 24 09:52:42 UTC 2020
Hi Liu,
On 23.07.20 18:02, Liu, Xin wrote:
> That is my intention too, but CompilerOracle doesn't exit JVM when it encounters parsing errors.
> It just exacts information from CompileCommand as many as possible. That makes sense because compiler "directives" are supposed to be optional for program execution.
>
> I do put the error message in parser's errorbuf. I set a flag "exit_on_error" to quit JVM after it dumps parser errors. yes, I treat undefined intrinsics as fatal errors.
> This behavior is from Nils comment: "I want to see an error on startup if the user has specified unknown intrinsic names." It is also consistent with JVM option -XX:ControlIntrinsic=.
Okay, thanks for the explanation! I would prefer consistency in error handling of compiler
directives, i.e., handle all parser failures the same way. But I leave it to Nils to decide.
Best regards,
Tobias
More information about the hotspot-runtime-dev
mailing list