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/55383] -Wcast-qual reports incorrect message Date: Mon, 10 Mar 2014 11:06:00 -0000 [thread overview] Message-ID: <bug-55383-4-B3VIjKmiOg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55383-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55383 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch --- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Magnus Reftel from comment #6) > Sorry, I'm not a GCC developer - just another user aflicted by the bug. Everybody can be a GCC developer. You don't need special powers, just some free time and willing to be. For such a small patch, you don't need any copyright assignment. Just check out svn trunk, set up a bootstrap, test without the patch, apply the patch, bootstrap and test with the patch and compare the results. (Check the gccfarming script here: http://gcc.gnu.org/wiki/ManuelL%C3%B3pezIb%C3%A1%C3%B1ez for all the details). If the patch does not produce any new FAILs in the testsuite, submit to gcc-patches with a changelog and ask the reviewer to commit it once accepted. (You don't even need a powerful computer to do all this, just get an account on the compile farm: http://gcc.gnu.org/wiki/CompileFarm ) >From gcc-bugs-return-445894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 10 11:27:05 2014 Return-Path: <gcc-bugs-return-445894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29722 invoked by alias); 10 Mar 2014 11:27:04 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 29666 invoked by uid 48); 10 Mar 2014 11:27:00 -0000 From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/60429] [4.7/4.8/4.9 Regression] Miscompilation (aliasing) with -finline-functions Date: Mon, 10 Mar 2014 11:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.8.2 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.7.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-60429-4-L4IRO0IWaV@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60429-4@http.gcc.gnu.org/bugzilla/> References: <bug-60429-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-03/txt/msg00763.txt.bz2 Content-length: 212 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`429 --- Comment #19 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Yes, looks like the reduced testcase is invalid and contains a few buffer overflows.
next prev parent reply other threads:[~2014-03-10 11:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-18 19:21 [Bug c/55383] New: " gcc.hall at gmail dot com 2012-11-18 21:15 ` [Bug c/55383] " manu at gcc dot gnu.org 2013-06-08 12:54 ` gerald at pfeifer dot com 2013-06-08 17:18 ` manu at gcc dot gnu.org 2014-03-10 10:43 ` magnus.reftel at gmail dot com 2014-03-10 10:52 ` manu at gcc dot gnu.org 2014-03-10 11:06 ` manu at gcc dot gnu.org [this message] 2014-03-10 15:35 ` gerald at pfeifer dot com 2014-03-11 6:54 ` magnus.reftel at gmail dot com 2014-03-11 7:00 ` magnus.reftel at gmail dot com 2014-03-11 12:48 ` magnus.reftel at gmail dot com 2014-03-18 7:59 ` magnus.reftel at gmail dot com 2014-03-18 12:48 ` manu at gcc dot gnu.org 2014-03-18 19:59 ` manu at gcc dot gnu.org 2014-03-18 20:06 ` manu at gcc dot gnu.org 2014-03-18 23:21 ` manu at gcc dot gnu.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-55383-4-B3VIjKmiOg@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).