From: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
To: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [PATCH, cpp] Fix pr61817 and 69391
Date: Tue, 05 Apr 2016 18:03:00 -0000 [thread overview]
Message-ID: <5703FE05.2020406@gmail.com> (raw)
In-Reply-To: <5703E64D.3090503@redhat.com>
On 05/04/16 17:22, Richard Henderson wrote:
> These two related PRs are all about remembering where a macro is expanded.
> Worse, we've got two competing goals -- the real location of the expansion, for
> __LINE__, and the virtual location of the expansion, for diagnostics.
>
> There seems to be no way to unify the two competing goals. If we simply "fix"
> the first, we break the second. Therefore, I resort to passing down both
> locations.
> +++ b/gcc/testsuite/gcc.dg/pr61817.c
> @@ -0,0 +1,19 @@
> +/* { dg-do compile } */
> +/* { dg-options "-std=c11 -ftrack-macro-expansion=0" } */
> +
Why use -ftrack-macro-expansion=0? This should work with =1, which is also the
default, no?
Cheers,
Manuel.
next prev parent reply other threads:[~2016-04-05 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 16:22 Richard Henderson
2016-04-05 18:03 ` Manuel López-Ibáñez [this message]
2016-04-05 18:28 ` Richard Henderson
2016-04-06 14:39 ` Jakub Jelinek
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=5703FE05.2020406@gmail.com \
--to=lopezibanez@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=rth@redhat.com \
/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).