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 preprocessor/60723] Line directives with incorrect system header flag
Date: Tue, 01 Apr 2014 09:51:00 -0000	[thread overview]
Message-ID: <bug-60723-4-0ykypgHXzG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60723-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60723

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Patches go to the gcc-patches mailing list for review. You will also need a
testcase formatted for inclusion on the testsuite and test your patch against
the GCC testsuite. See also: http://gcc.gnu.org/contribute.html

> In a function-like macro expansion, regular tokens are line-marked as being
> expanded at the opening parenthesis, while builtins are line-marked as being
> expanded at the closing parenthesis (both of these choices are reasonable,
> though the inconsistency is probably a design flaw). When a non-builtin
> follows a builtin in a multiline macro call, the line numbers of the tokens
> are inconsistent, forcing a line directive to be inserted.

I don't see how your patch fixes this inconsistency.
>From gcc-bugs-return-448011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Apr 01 09:57:09 2014
Return-Path: <gcc-bugs-return-448011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2294 invoked by alias); 1 Apr 2014 09:57:09 -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 2244 invoked by uid 55); 1 Apr 2014 09:57:06 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60363] [4.9 Regression]: logical_op_short_circuit, gcc.dg/tree-ssa/ssa-dom-thread-4.c scan-tree-dump-times dom1 "Threaded" 4
Date: Tue, 01 Apr 2014 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60363-4-eHmN9gU1AH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60363-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-04/txt/msg00031.txt.bz2
Content-length: 455

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`363

--- Comment #12 from amker at gcc dot gnu.org ---
Author: amker
Date: Tue Apr  1 09:56:29 2014
New Revision: 208980

URL: http://gcc.gnu.org/viewcvs?rev 8980&root=gcc&view=rev
Log:

    PR target/60363
    * gcc.target/tree-ssa/ssa-dom-thread-4.c: Xfail for
    logical_op_short_circuit targets.


Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c


  parent reply	other threads:[~2014-04-01  9:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  1:37 [Bug preprocessor/60723] New: " nicholas.ormrod at hotmail dot com
2014-04-01  1:37 ` [Bug preprocessor/60723] " nicholas.ormrod at hotmail dot com
2014-04-01  1:38 ` nicholas.ormrod at hotmail dot com
2014-04-01  1:39 ` nicholas.ormrod at hotmail dot com
2014-04-01  9:51 ` manu at gcc dot gnu.org [this message]
2014-04-01 15:30 ` nicholas.ormrod at hotmail dot com
2014-06-10  6:21 ` nicholas.ormrod at hotmail dot com
2014-06-10 13:18 ` matt at godbolt dot org
2014-06-15 22:31 ` nicholas.ormrod at hotmail dot com
2014-06-25 15:32 ` dodji at gcc dot gnu.org
2014-07-01  9:18 ` dodji at gcc dot gnu.org
2014-07-01 14:13 ` christophe.lyon at st dot com
2014-07-01 14:16 ` christophe.lyon at st dot com
2014-07-02 13:43 ` dodji at gcc dot gnu.org
2014-07-02 13:44 ` dodji at gcc dot gnu.org
2014-07-03 13:48 ` christophe.lyon at st dot com
2014-07-16  8:58 ` dodji at gcc dot gnu.org
2014-07-16 10:34 ` dodji at gcc dot gnu.org
2014-07-16 13:38 ` dodji at gcc dot gnu.org
2014-07-17  3:36 ` nicholas.ormrod at hotmail dot com
2014-07-22  9:55 ` ktkachov at gcc dot gnu.org
2014-07-24  8:22 ` ktkachov at gcc dot gnu.org
2015-02-05 10:07 ` jakub at gcc dot gnu.org
2021-03-26 23:31 ` egallager at gcc dot gnu.org
2022-10-12 22:16 ` cvs-commit 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-60723-4-0ykypgHXzG@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: link
Be 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).