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: Tue, 18 Mar 2014 12:48:00 -0000 [thread overview] Message-ID: <bug-55383-4-ifcxF0pClI@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 --- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Magnus Reftel from comment #12) > Any suggestions on how to progress with this one? Looking at the testcases modified by the patch, I don't know why there is no test for volatile (which is what triggers this bug). I will take a look at the output of the testsuite this weekend. It is probable that there is a testcase for this, but the test matching text is not precise enough. Once I check this, I will commit the patch since it was approved by Joseph here: http://gcc.gnu.org/ml/gcc-patches/2014-03/msg00532.html >From gcc-bugs-return-446699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 18 13:01:00 2014 Return-Path: <gcc-bugs-return-446699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27234 invoked by alias); 18 Mar 2014 13:01:00 -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 27194 invoked by uid 48); 18 Mar 2014 13:00:57 -0000 From: "raghupv30 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60459] Crash seen in _Unwind_VRS_Pop() for ARM platform Date: Tue, 18 Mar 2014 13:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: raghupv30 at gmail dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity Message-ID: <bug-60459-4-XUjn8CKR4B@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60459-4@http.gcc.gnu.org/bugzilla/> References: <bug-60459-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/msg01568.txt.bz2 Content-length: 287 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`459 Raghu <raghupv30 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical
next prev parent reply other threads:[~2014-03-18 12:48 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 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 [this message] 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-ifcxF0pClI@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).