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: [Patch] Remove gccbug from bugreport.texi, take 3

> > > ! @item
> > > ! If you send examples of assembler code output from GCC,
> > > ! please use @option{-g} when you make them.  The debugging information
> > > ! includes source line numbers which are essential for correlating the
> > > ! output with the input.
> > 
> > bugs.html currently lacks this piece of information.
> -fverbose-asm may also be useful in such circumstances.

I had meant to drop this piece just as the thing about debug_rtx by
purpose. I certainly haven't seen a PR in which these were applicable, and
if we'd really need them we can still ask for this information. I believe
it is more important to keep the instructions short. If we offer too much
good advice about how to send in PRs, nobody will read it and we'll end up
with worse reports.

Do y'all really think this needs to be in the instructions?


Wolfgang Bangerth              email:  

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