This is the mail archive of the
mailing list for the GCC project.
Re: [trunk<-vta] Re: [vta,vta4.3,trunk?] introduce -fcompare-debug
Alexandre Oliva <email@example.com> writes:
> Sure we do have a number of internal property checkers that are
> controlled through configure-time options. They can be turned on or off
> because they do have a run-time impact to support. This one doesn't, so
> it doesn't hurt at all to always have it there, so that it can be
> enabled or disabled like any of the other hundreds of flags that are
> designed exclusively to aid in compiler debugging, and that are
> nevertheless exposed to users.
> And then, having it as a compile-time option rather than a
> configure-time option means we can get better coverage from our
> bootstrap checking without significant impact. E.g., we can build
> stage2 without debug info (builds much faster with the unoptimized
> stage1) and then build stage3 with -fcompare-debug (must still produce
> the same output to pass bootstrap compare, but can still check that the
> internal representation doesn't change because of -g).
I don't fully understand what the proposed option does, so I don't know
if this comment applies: if this is for a run-time option to improve
checking, then it should not be a -f option, it should be a --param. -f
options are for users. --param options are for developers.