https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100464
--- Comment #13 from Chengnian Sun <cnsun at uwaterloo dot ca> ---
(In reply to Jakub Jelinek from comment #8)
> gcc has the -fcompare-debug option, which compiles twice, once with -g and
> once with -g -gtoggle and compares result, anything that fails with that
> option with an error about debug vs. non-debug differences or potential
> differences is a bug.
Hi Jakub,
Is the following flag is correct usage of -fcompare-debug?
$ gcc -fcompare-debug -O3 t.c
Also, what is the output or the exit code if gcc finds an inconsistency in
debug info? Is there an internal compiler error?
Thanks.
