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/63326] whether a #pragma is a statement depends on the type of pragma Date: Wed, 22 Oct 2014 14:11:00 -0000 [thread overview] Message-ID: <bug-63326-4-IPz0TqWOGw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63326-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326 --- Comment #12 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to steveren from comment #11) > So assuming it's not actually beyond somebody completely unfamiliar with the > innards of gcc, what would be the response to a patch which changed #pragma > message from 'statement' to 'not-a-statement'? I think that even if not a definitive solution, it would be a positive step towards understanding what would it take to change the behavior for specific #pragmas (since we cannot change how OMP #pragmas behave). >From gcc-bugs-return-464658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 22 14:11:58 2014 Return-Path: <gcc-bugs-return-464658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18570 invoked by alias); 22 Oct 2014 14:11:58 -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 18527 invoked by uid 48); 22 Oct 2014 14:11:53 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63600] [5 Regression] ice in ix86_expand_sse2_abs Date: Wed, 22 Oct 2014 14:14: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: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-63600-4-J3ZwSzD3VO@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63600-4@http.gcc.gnu.org/bugzilla/> References: <bug-63600-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-10/txt/msg01679.txt.bz2 Content-length: 286 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc600 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I would have expected VI instead of IV in the iterator name, but I never understood the rules for i?86 iterator names. And, you want the testcase in the testsuite too.
next prev parent reply other threads:[~2014-10-22 14:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-22 6:37 [Bug c/63326] New: pragma GCC causes wrong code generation dietmar.schindler@manroland-web.com 2014-09-22 6:41 ` [Bug c/63326] " pinskia at gcc dot gnu.org 2014-09-24 11:46 ` dietmar.schindler@manroland-web.com 2014-09-24 14:36 ` manu at gcc dot gnu.org 2014-09-24 15:41 ` [Bug c/63326] whether a #pragma is a statement depends on the type of pragma pinskia at gcc dot gnu.org 2014-10-21 23:20 ` pinskia at gcc dot gnu.org 2014-10-22 8:37 ` rguenth at gcc dot gnu.org 2014-10-22 9:12 ` jakub at gcc dot gnu.org 2014-10-22 12:50 ` manu at gcc dot gnu.org 2014-10-22 14:08 ` q.gcc@rsn-tech.co.uk 2014-10-22 14:11 ` manu at gcc dot gnu.org [this message] 2020-03-27 18:40 ` pinskia at gcc dot gnu.org 2020-03-27 18:47 ` romain.geissler at amadeus dot com 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-07-20 19:40 ` msebor at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 7:27 ` rguenth at gcc dot gnu.org 2023-10-10 12:13 ` pinskia at gcc dot gnu.org 2024-01-24 17:27 ` pinskia 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-63326-4-IPz0TqWOGw@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).