From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix preprocessing of macro expanded pragmas (take 2)
Date: Wed, 27 Feb 2008 00:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0802270020070.12480@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20080226235455.GK24887@devserv.devel.redhat.com>
On Tue, 26 Feb 2008, Jakub Jelinek wrote:
> 2008-02-26 Jakub Jelinek <jakub@redhat.com>
>
> * c-ppoutput.c (scan_translation_unit): Handle CPP_PRAGMA
> and CPP_PRAGMA_EOL.
> * c-pragma.c (pragma_ns_name): New typedef.
> (registered_pp_pragmas): New variable.
> (c_pp_lookup_pragma): New function.
> (c_register_pragma_1): If flag_preprocess_only, do nothing
> for non-expanded pragmas, for expanded ones push pragma's
> namespace and name into registered_pp_pragmas vector.
> (c_invoke_pragma_handler): Register OpenMP pragmas even when
> flag_preprocess_only, don't register GCC pch_preprocess
> pragma if flag_preprocess_only.
> * c-opts.c (c_common_init): Call init_pragma even if
> flag_preprocess_only.
> * c-pragma.c (c_pp_lookup_pragma): New prototype.
> * config/darwin.h (DARWIN_REGISTER_TARGET_PRAGMAS): Don't call
> cpp_register_pragma if flag_preprocess_only.
>
> * gcc.dg/gomp/preprocess-1.c: New test.
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2008-02-27 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 14:35 Patch ping Jakub Jelinek
2008-02-20 16:26 ` Tom Tromey
2008-02-27 0:58 ` [PATCH] Fix preprocessing of macro expanded pragmas (take 2) Jakub Jelinek
2008-02-27 0:58 ` Joseph S. Myers [this message]
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=Pine.LNX.4.64.0802270020070.12480@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tromey@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).