This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [trunk<-vta] Re: [vta,vta4.3,trunk?] introduce -fcompare-debug

On Jun  2, 2009, Ian Lance Taylor <> wrote:

> My point is simply that this option, if we include it, would never be
> for end-users of gcc (who are, yes, themselves developers), and should
> be named and documented accordingly.

I think I understand the issue, but I don't understand what
improvements, if any, are needed.  It is already documented right next
to the various -fdump-* options, which IIUC are for the same target
developer base.

OTOH, our docs currently conflate options to choose how GCC is to
output debug information for programs it compiles, and options to choose
what internal information GCC is to dump to help debug itself.

If we were to split them up, -fcompare-debug would certainly fit better
in the second rather than the former, but as it stands, it's documented
at the best existing place, no?

I welcome suggestions for improvement of the documentation, say, if it's
lacking or overspecified or aimed at the wrong target or somesuch.

Alexandre Oliva, freedom fighter
You must be the change you wish to see in the world. -- Gandhi
Be Free! --   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]