GCC_JIT_BOOL_OPTION_DUMP_EVERYTHING is slow
David Malcolm
dmalcolm@redhat.com
Wed Jan 1 00:00:00 GMT 2014
On Fri, 2014-02-14 at 10:14 +0000, Philip Herron wrote:
> What happens at different optimization levels like -O1/2/3 and is
> there a way to turn on specific options like that i know i read that
> the global state makes that fail.
Right now all that's exposed is GCC_JIT_INT_OPTION_OPTIMIZATION_LEVEL,
and that value from 0 to 3 corresponds directly to setting -O0 through
-O3. There isn't yet a way to turn specific optimizations off or on, or
to build custom passes.
If you can reliably crash the jit due to lack of state-cleanup, that's a
bug, naturally. I'd rather fix such bugs than put in flags to avoid
them. That said, one can inject extra command line options the nasty
way by hacking up playback::context::compile in internal-error.c, which
currently sets options by constructing a command line, then calling
toplev_main (which is inelegant, and yet another area to clean up) - you
can hack in extra flags there if need be - though as I said, it'd be
better to fix the state-management bugs.
[snip]
Hope this is helpful
Dave
More information about the Jit
mailing list