debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64)

[Joern Rennecke]

> In the case of heavily intermingled code, the line number info may
> look like (i've omitted is_stmt, basic_block, and other registers, for
> simplicity):
> 
> Line advance            Address advance
> 0                       1
> -1                      1
> 2                       1
> -1                      1
> etc

So that's the way gdb handles it right now.  Which can mean that
optimized code is so tedious to debug for some applications and targets
that you try to avoid it at all costs.  Not what I'd call 'not being able
to tell the difference'.