--- Additional Comments From dberlin at gcc dot gnu dot org 2005-03-02
16:23 ---
(In reply to comment #5)
> Subject: Re: g++ generates incomplete debug information for given testcase
with optimization
>
>
> Keeping in mind my previous email that I'm not familiar with how gcc records
>
--- Additional Comments From fnf at specifixinc dot com 2005-03-02 16:01
---
Subject: Re: g++ generates incomplete debug information for given testcase
with optimization
On Tuesday 01 March 2005 22:49, dberlin at gcc dot gnu dot org wrote:
> In particular, it is possible we are missi
--- Additional Comments From fnf at specifixinc dot com 2005-03-02 16:01
---
Subject: Re: g++ generates incomplete debug information for given testcase
with optimization
On Tuesday 01 March 2005 22:49, dberlin at gcc dot gnu dot org wrote:
> In particular, it is possible we are missi
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-03-02
04:49 ---
Debug output for inlining, etc, isn't actually driven by the callgraph, so yes,
it can get out of sync with reality (it's not supposed to, but it does). In
particular, it is possible we are missing some in
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-01
21:47 ---
Is there a way to produce the output you gave easily?
Also why do you think gcc should produce good debug information with
optimizations since scheduling
can change ording of instructions so it causes DW_T
--- Additional Comments From fnf at diveadx dot com 2005-03-01 21:21
---
Subject: Re: g++ generates incomplete debug information for given testcase
with optimization
On Tuesday 01 March 2005 15:16, pinskia at gcc dot gnu dot org wrote:
> What version of gcc can you reproduce this with
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-01
21:16 ---
What version of gcc can you reproduce this with?
Give the output of "gcc -v"?
--
What|Removed |Added
-
