public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Sean McNeil <sean@mcneil.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: preprocessor/2948 Date: Tue, 29 May 2001 09:46:00 -0000 [thread overview] Message-ID: <20010529164604.2415.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR preprocessor/2948; it has been noted by GNATS. From: Sean McNeil <sean@mcneil.com> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/2948 Date: Tue, 29 May 2001 09:40:39 -0700 The pragmas are indeed getting passed through by the cpp0. So why would they compile differently in the two cases? This is very strange. It is related to that #pragma, though. Perhaps the cpp is told to parse things differently? Sean Neil Booth wrote: > Sean McNeil wrote:- > > > This has puzzled me for a while and I've tried several additional > > things as we've been discussing this. I noticed that the cc1plus > > program installs handlers for various pragmas and discovered a > > #pragma implementation in PlotFile.cpp. When I remove this pragma, > > compilation is as I expected. > > Great, thanks for persisting. > > > HOWEVER.... there is no template code that exists within the ttt.ii > > file (after preprocessor) and adding a #pragma implementation to > > ttt.cc (copy of ttt.ii) doesn't reproduce the problem either. So I > > am still at a loss as to why > > Hmmm. This doesn't sound good. Are you saying that the #pragma does > not exist in the -E preprocessed output? If so, that's a bug. Most > pragmas are not handled or understood by CPP, so it must pass them > through in the preprocessed output unchanged. > > > 1) there is a #pragma implementation in this file (Something I do > > not expect anyone on > the gcc team to answer :). > > I have no idea. I'm not really sure what the pragma does, either, > though I know it's to do with template instantiation. > > > 2) why code is generated for the pragma even though > > -fexternal-templates was not defined. > > Again, this would require me to understand exactly what it does. > > > I suppose what it boils down to is it's not a cpp problem, but a > > cc1plus problem. Should this be reassigned? > > Probably, provided that CPP is passing through the pragma. I'll > do that when we get just a little closer. > > Does this code work, both ways, with 2.95.2 or 2.95.3? If so, it's a > regression, and I'll mark it high priority and it should get done for > 3.0. > > Neil.
next reply other threads:[~2001-05-29 9:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-29 9:46 Sean McNeil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-29 18:26 preprocessor/2948 Sean McNeil 2001-05-29 18:06 preprocessor/2948 Sean McNeil 2001-05-29 10:26 preprocessor/2948 Neil Booth 2001-05-28 23:46 preprocessor/2948 Neil Booth 2001-05-28 18:56 preprocessor/2948 Sean McNeil 2001-05-28 15:26 preprocessor/2948 Neil Booth 2001-05-27 10:36 preprocessor/2948 Sean McNeil 2001-05-27 0:46 preprocessor/2948 Neil Booth 2001-05-26 8:46 preprocessor/2948 Sean McNeil 2001-05-26 1:16 preprocessor/2948 neil
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=20010529164604.2415.qmail@sourceware.cygnus.com \ --to=sean@mcneil.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).