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++/53431] C++ preprocessor ignores #pragma GCC diagnostic Date: Mon, 20 Jul 2015 09:38:00 -0000 [thread overview] Message-ID: <bug-53431-4-Lt0Cut8Vx9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53431-4@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3561 bytes --] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431 --- Comment #12 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Allan Chandler from comment #11) > Now you've done it. This was reported over three years ago and now it's > affected someone on Stack Overflow. You guys are in for it now :-) Unfortunately, the C/C++ FEs in GCC have very very few developers relative to their importance and amount work they require. There is a patch in comment #10, but it requires some additional work for which I do not have enough free time. If you or someone else has some free time to finish this work, this is how I would proceed: 1. Try to figure out why the preprocessor removes the pragmas (and not other #-directives) 2. If you cannot figure it out, ask in gcc@ with explicit CC to C/C++/libcpp maintainers (see MAINTAINERS file). 3. Complete the patch, bootstrap®ression test, add a Changelog, submit to gcc-patches and ping until it is approved. More details: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps Otherwise, given that this hasn't been fixed in more than 4 years (see PR48914), it seems likely that active developers have higher priority things to work on and it will remain unfixed until some new volunteer steps up to the task. If/When I have a little free time to work on GCC, there are at least a couple of other bugs I would rather fix before this one. >From gcc-bugs-return-492817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 20 09:40:31 2015 Return-Path: <gcc-bugs-return-492817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 117016 invoked by alias); 20 Jul 2015 09:40:31 -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 116717 invoked by uid 48); 20 Jul 2015 09:40:27 -0000 From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/66915] [6 Regression] FAIL: gcc.dg/fixed-point/unary.c execution test on arm Date: Mon, 20 Jul 2015 09:40: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: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ktkachov at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: attachments.created Message-ID: <bug-66915-4-XvakCBXVjI@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66915-4@http.gcc.gnu.org/bugzilla/> References: <bug-66915-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: 2015-07/txt/msg01707.txt.bz2 Content-length: 252 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf915 --- Comment #2 from ktkachov at gcc dot gnu.org --- Created attachment 36015 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id6015&actioníit Diff between good and bad versions of the assembly
next prev parent reply other threads:[~2015-07-20 9:38 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-21 8:03 [Bug c++/53431] New: C++ preprocessor ignores #pragma GCC diagnostic ignored "-Wundef" ml.lattuada at libero dot it 2013-02-17 17:04 ` [Bug c++/53431] " rainarchitect at gmail dot com 2013-03-03 4:10 ` markus at oberhumer dot com 2013-07-12 9:20 ` nomegenerico at email dot it 2013-11-16 18:13 ` rainarchitect at gmail dot com 2013-11-16 19:51 ` manu at gcc dot gnu.org 2013-11-16 20:23 ` manu at gcc dot gnu.org 2014-09-05 17:42 ` [Bug c++/53431] C++ preprocessor ignores #pragma GCC diagnostic manu at gcc dot gnu.org 2015-06-03 8:27 ` manu at gcc dot gnu.org 2015-07-20 9:38 ` manu at gcc dot gnu.org [this message] 2015-07-22 0:00 ` noloader at gmail dot com 2015-07-22 10:51 ` redi at gcc dot gnu.org 2015-07-22 11:24 ` noloader at gmail dot com 2015-07-23 10:34 ` noloader at gmail dot com 2015-07-23 10:47 ` redi at gcc dot gnu.org 2015-07-23 11:32 ` manu at gcc dot gnu.org 2015-07-23 13:20 ` manu at gcc dot gnu.org 2015-07-23 23:26 ` noloader at gmail dot com 2015-07-30 17:22 ` miyuki at gcc dot gnu.org 2021-02-27 11:24 ` noloader at gmail dot com 2021-06-03 12:04 ` redi at gcc dot gnu.org 2021-10-06 14:40 ` jakub at gcc dot gnu.org 2021-12-01 17:43 ` egallager at gcc dot gnu.org 2021-12-04 17:48 ` lhyatt at gcc dot gnu.org 2021-12-19 11:55 ` pinskia at gcc dot gnu.org 2021-12-19 19:50 ` manu at gcc dot gnu.org 2021-12-24 21:29 ` lhyatt at gcc dot gnu.org 2022-03-23 0:58 ` pinskia at gcc dot gnu.org 2022-05-25 13:38 ` lhyatt at gcc dot gnu.org 2022-06-29 16:08 ` lhyatt at gcc dot gnu.org 2022-07-06 19:40 ` cvs-commit at gcc dot gnu.org 2022-07-06 19:42 ` lhyatt at gcc dot gnu.org 2022-07-06 22:59 ` lhyatt at gcc dot gnu.org 2022-11-08 22:28 ` redi at gcc dot gnu.org 2022-11-09 0:05 ` markus at oberhumer 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-53431-4-Lt0Cut8Vx9@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).