https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79659
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
There's related ICE in this are:
echo '' | ./xgcc -B. -x c - -c -flifetime-dse=1111
<stdin>:1:0: internal compiler error: in cl_optimization_save, at
options-save.c:121
0xb1ef92 cl_optimization_save(cl_optimization*, gcc_options*)
/home/marxin/Programming/gcc2/objdir/gcc/options-save.c:121
0xee4b8a build_optimization_node(gcc_options*)
../../gcc/tree.c:12382
0x65f275 process_options
../../gcc/toplev.c:1613
0x65f275 do_compile
../../gcc/toplev.c:1940
because we generate assert for optimization options:
gcc_assert (IN_RANGE (opts->x_flag_lifetime_dse, -128, 127));
I'm wondering whether cutting values out of possible range to maximum (or
minimum) would be desired?