public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59472] Many warnings "type of 'X' does not match original declaration" when linking with libstdc++ static library compiled with -flto Date: Wed, 22 Jan 2014 21:36:00 -0000 [thread overview] Message-ID: <bug-59472-4-VeEnCMpUNU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59472-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59472 Marc Glisse <glisse at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2014-01-22 Component|lto |libstdc++ Ever confirmed|0 |1 --- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> --- Same here (CXXFLAGS_FOR_TARGET="-O2 -g -flto -ffat-lto-objects" after a trivial fix for PR 43538): /data/repos/gcc/trunk/libstdc++-v3/src/c++98/ios_init.cc:56:33: warning: type of 'buf_wcerr' does not match original declaration [enabled by default] extern stdio_filebuf<wchar_t> buf_wcerr; ^ /data/repos/gcc/trunk/libstdc++-v3/src/c++98/globals_io.cc:105:17: note: previously declared here fake_wfilebuf buf_wcerr; ^ etc. Reassigning to libstdc++ because the warnings seem to say the truth.
next prev parent reply other threads:[~2014-01-22 21:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-11 16:06 [Bug lto/59472] New: " d.g.gorbachev at gmail dot com 2014-01-22 21:36 ` glisse at gcc dot gnu.org [this message] 2014-05-08 13:24 ` [Bug libstdc++/59472] " redi at gcc dot gnu.org 2014-05-08 13:32 ` redi at gcc dot gnu.org 2014-06-24 16:38 ` paul at scruby dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-59472-4-VeEnCMpUNU@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).