This is the mail archive of the gcc@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: O0 cleanup_cfg vs debuggability


On Thu, Aug 12, 2004 at 03:05:40PM +0200, Olivier Hainque wrote:
> Hello James,
> 
> Regarding a breakpoint on "break;" not hit, you suggested:
> 
> > In gcc-3.4, I think you can solve this by redefining what a forwarder 
> > block is, or how we handle them.  See forwarder_block_p in cfganal.c. 
> [...]
> 
>  I have experimented the first alternative, preventing a block from beeing
>  flagged as a forwarded if it contains a line number note and we're not
>  optimizing.
>  
>  It unfortunately has a consequence which seems undesireable to me: we get
>  different code depending on whether -g is provided or not.
> 
>  Is that indeed a valid concern ?

Absolutely.  Don't conditionalize it on -g; conditionalize it on
!optimize.

-- 
Daniel Jacobowitz


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