https://sourceware.org/bugzilla/show_bug.cgi?id=26847
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment #1
https://sourceware.org/bugzilla/show_bug.cgi?id=26841
Nick Clifton changed:
What|Removed |Added
CC||nickc at redhat dot com
--- Comment #1
https://sourceware.org/bugzilla/show_bug.cgi?id=26841
--- Comment #2 from Tom de Vries ---
(In reply to Nick Clifton from comment #1)
> Created attachment 12944 [details]
> Proposed patch
>
> Hi Tom,
>
> It seems to me that we ought to keep the relocations.
>
> So please could you try out
https://sourceware.org/bugzilla/show_bug.cgi?id=26841
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> So, AFAIU it's already questionable that labels are allowed in a dwo section
> in the first place. If we assume that they're not allowed, we can still
> allow
https://sourceware.org/bugzilla/show_bug.cgi?id=26841
--- Comment #4 from Nick Clifton ---
Created attachment 12945
--> https://sourceware.org/bugzilla/attachment.cgi?id=12945&action=edit
Proposed patch
Hi Tom,
> Alternatively, we could choose not to make things easier for the compiler,
> an
https://sourceware.org/bugzilla/show_bug.cgi?id=26841
--- Comment #5 from Tom de Vries ---
(In reply to Nick Clifton from comment #4)
> Created attachment 12945 [details]
> Proposed patch
>
> Hi Tom,
>
> > Alternatively, we could choose not to make things easier for the compiler,
> > and
> >
https://sourceware.org/bugzilla/show_bug.cgi?id=26850
Bug ID: 26850
Summary: as -g: remove non-executable sections' contribution
from DW_AT_ranges
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Sever
https://sourceware.org/bugzilla/show_bug.cgi?id=26847
--- Comment #2 from Tom Tromey ---
I didn't try it, but it looks like exactly what I'd like :)
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
Comment by aa...@google.com:
Today's coverage build failure is an issue in upstream llvm-cov, we have
reverted the clang roll for now and hopefully coverage build should come green
tonight. Follow https://github.com/google/oss-fuzz/issues/4608 for more
updates.
Affected issues:
Issue 27030
