This is the mail archive of the gcc-patches@gcc.gnu.org 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: PR 23551: why should we coalesce inlined variables?


On 10 July 2007 19:41, H.J. Lu wrote:

> On Tue, Jul 10, 2007 at 07:32:25PM +0100, Dave Korn wrote:
>>   I'm just not convinced of the value of debugging information that
>> describes what the code could have been rather than what it actually is. 
>> I'm not convinced by your use cases.  Someone who wants to analyze their
>> code as it is written rather than as it is compiled should be using static
>> analysis or generating debug from a -O0 compilation.
> 
> When I debug binutils, I have to use "-g -O0". Otherwise, I can't
> put breakpoints on static functions which are inlined with -O1.

  Yep, that's what I do too.  I don't expect to be able to meaningfully
interact with stuff that has been optimised away, for the very simple reason
that it just is not there!

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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