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 18:26:00 -0000	[thread overview]
Message-ID: <20010530012600.20939.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c++/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 18:22:00 -0700

 I found the following error when I compile via. the 2 stage mechanism with gcc
 2.95.3:
 
 arm-wrs-vxworks-g++ -v -mcpu=arm8 -mapcs-32 -mlittle-endian -ansi -nostdinc
 -fno-implicit-templates -DVXW_EXPLICIT_TEMPLATES -O2 -mno-sched-prolog
 -I/usr/arm-wrs-vxworks/target/h -DCPU=ARMARCH4 -DARMEL -fno-exceptions -o
 /tmp/ttt.o -c /tmp/ttt.cc
 
 PlotFile.cpp:67: `#pragma implementation' can only appear at top-level
 
 Sean
 
 Neil Booth wrote:
 
 > Sean McNeil wrote:-
 >
 > >  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?
 >
 > Are the pragmas merely
 >
 > #pragma implementation
 >
 > or are they
 >
 > #pragma implementation "filename"
 >
 > ?  I think it's an issue with file names not comparing as strings
 > properly because of path information, or something like that.  Does
 > that give you a clue?
 >
 > Is there a
 >
 > #pragma interface
 >
 > somewhere to match the #pragma implementation?
 >
 > Is this a 2.95 regression?  I'm going to re-file this as a C++ bug.
 >
 > Neil.
 


             reply	other threads:[~2001-05-29 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-29 18:26 Sean McNeil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-29 18:06 preprocessor/2948 Sean McNeil
2001-05-29 10:26 preprocessor/2948 Neil Booth
2001-05-29  9:46 preprocessor/2948 Sean McNeil
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=20010530012600.20939.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: 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).