From: Joseph Myers <joseph@codesourcery.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
Dodji Seketeli <dodji@redhat.com>,
Marek Polacek <polacek@redhat.com>
Subject: Re: [RFC PATCH] parse #pragma GCC diagnostic in libcpp
Date: Wed, 23 Sep 2015 23:43:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1509232259390.10585@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAESRpQBMWRCEwBoaUHxKNeYDQcBP9e4-nmZ1S622SwH8TnLeYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Sun, 20 Sep 2015, Manuel López-Ibáñez wrote:
> PING^2: https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02414.html
>
> On 21 August 2015 at 19:41, Manuel López-Ibáñez <lopezibanez@gmail.com> wrote:
> > Any comments on this? https://gcc.gnu.org/ml/gcc-patches/2015-07/msg02414.html
> >
> > I don't see any other way to fix these PRs, but I don't know how to
> > keep the pragmas from being deleted by the preprocessor.
I'd suppose you want a new type of pragma, that acts like a combination of
a deferred one and one for which a handler is called immediately by
libcpp. libcpp would call the handler but also create a CPP_PRAGMA token.
The front-end code calling pragma handlers would need to know to do
nothing with such pragmas; the token would only be for textual
preprocessor output.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-09-23 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 4:43 Manuel López-Ibáñez
2015-08-21 17:44 ` Manuel López-Ibáñez
2015-09-20 18:23 ` Manuel López-Ibáñez
2015-09-23 23:43 ` Joseph Myers [this message]
2015-09-25 15:58 ` Dodji Seketeli
2015-09-27 12:03 ` Manuel López-Ibáñez
2015-09-27 14:45 ` Dodji Seketeli
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=alpine.DEB.2.10.1509232259390.10585@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=lopezibanez@gmail.com \
--cc=polacek@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).