https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #6 from Eric Gallager ---
(In reply to Paul Scruby from comment #5)
> Is there a patch to fix or suppress the warnings when link-time optimizing
> to libstdc++.a ? I'm using gcc4.8.2, but I'm happy to upgrade to gcc4.9 if
> this rele
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #7 from Paul Scruby ---
Feel free to close this ticket.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
>
> --- Comment #6 from Eric Gallager ---
> (In reply to Paul Scruby from comment #5)
>> Is there a patch to fix or suppres
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #8 from Jonathan Wakely ---
I think it's worth keeping open for my suggestion in comment 3 (which I'd
forgotten about).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
Marc Glisse changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
Paul Scruby changed:
What|Removed |Added
CC||paul at scruby dot com
--- Comment #2 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #3 from Jonathan Wakely ---
(In reply to Marc Glisse from comment #1)
> Reassigning to libstdc++ because the warnings seem to say the truth.
They do tell the truth.
We use char arrays for good reason (see the comment in src/c++98/glo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #4 from Jonathan Wakely ---
That should work for the streambufs, it's not so simple for the standard stream
objects though, as they're user-visible and we declared their (pretend) types
in .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472
--- Comment #5 from Paul Scruby ---
Is there a patch to fix or suppress the warnings when link-time optimizing to
libstdc++.a ? I'm using gcc4.8.2, but I'm happy to upgrade to gcc4.9 if this
release is more likely to get fixed first?