public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44774] -Werror=edantic Date: Fri, 17 Feb 2012 00:35:00 -0000 [thread overview] Message-ID: <bug-44774-4-xioKA5bP5P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44774-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44774 --- Comment #15 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-02-17 00:22:21 UTC --- Created attachment 26688 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26688 patch Bootstrapped and regression tested, but without documentation updated or testcase. Anyway, it is probably too late for 4.7 and I don't know when I will have time to pick this up again, so anyone feel free to take it/improve it.
next prev parent reply other threads:[~2012-02-17 0:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44774-4@http.gcc.gnu.org/bugzilla/> 2011-03-23 9:35 ` redi at gcc dot gnu.org 2011-04-19 15:17 ` redi at gcc dot gnu.org 2012-02-17 0:35 ` manu at gcc dot gnu.org [this message] 2012-04-22 19:18 ` manu at gcc dot gnu.org 2012-04-22 19:58 ` manu at gcc dot gnu.org 2010-07-01 21:40 [Bug c/44774] New: -Werror=edantic manu at gcc dot gnu dot org 2010-07-01 21:42 ` [Bug c/44774] -Werror=edantic manu at gcc dot gnu dot org 2010-07-01 21:54 ` manu at gcc dot gnu dot org 2010-07-02 1:23 ` joseph at codesourcery dot com 2010-07-02 6:59 ` manu at gcc dot gnu dot org 2010-07-02 8:08 ` manu at gcc dot gnu dot org 2010-07-02 9:22 ` jakub at gcc dot gnu dot org 2010-07-02 10:56 ` manu at gcc dot gnu dot org 2010-07-02 12:18 ` paolo dot carlini at oracle dot com 2010-07-02 14:24 ` manu at gcc dot gnu dot org 2010-07-02 15:22 ` paolo dot carlini at oracle dot com 2010-07-04 1:46 ` joseph at codesourcery dot com 2010-07-04 8:27 ` manu at gcc dot gnu dot org
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-44774-4-xioKA5bP5P@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).