https://sourceware.org/bugzilla/show_bug.cgi?id=26701
--- Comment #3 from Kib ---
(In reply to Nick Clifton from comment #1)
> there are several ways to work around the problem without
> modifying the linker. My stance is: why introduce new code, and
> potentially new bugs, to the linker
https://sourceware.org/bugzilla/show_bug.cgi?id=26701
Kib changed:
What|Removed |Added
CC||vampyrebat at gmail dot com
--
You are
http://sourceware.org/bugzilla/show_bug.cgi?id=12017
--- Comment #6 from Kib 2012-06-19 00:55:06 UTC
---
(In reply to comment #5)
> the warning isn't coming from the compiler, it's coming from the linker
Yes, I said exactly that in comment #1. I assumed, however, that the compiler
would pass t
http://sourceware.org/bugzilla/show_bug.cgi?id=12017
--- Comment #4 from Kib 2012-06-15 21:03:30 UTC
---
(In reply to comment #2)
> disabling all warnings generated via .gnu.warning
> sections is a very bad idea.
Since the compiler already has a switch to suppress ALL warnings, a switch to
supp
