https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to krux from comment #20)
> Thanks your patch worked!
>
> Just fyi: llvm-dwarfdump doesn't understand call-site info:
> https://bugs.llvm.org/show_bug.cgi?id=41846
> Not sure if it's relevant.
So, what's the status here?
I think
* we conclude that the revision bisected was not actually responsible for the
issue underlying (but caused it to be exposed).
* llvm-dwarfdump output isn't reliable as an indication of the problem
- do you have dwarfdump?
- can you use objdump -W<some section> ?
* we can now -save-temps for the case(s) of interest.
* I'm assuming that the problem is not "fixed" ? (have to verified that on
current trunk?)
