public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/3260: #include __FILE__ broken
Date: Tue, 19 Jun 2001 07:16:00 -0000 [thread overview]
Message-ID: <200106191414.f5JEERe08361@D65.suse.de> (raw)
>Number: 3260
>Category: preprocessor
>Synopsis: #include __FILE__ broken
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Tue Jun 19 07:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:
>Release: 3.0 20010611 (prerelease)
>Organization:
>Environment:
System: Linux D65 2.4.4 #1 SMP Wed Jun 13 21:43:48 GMT 2001 ia64 unknown
Architecture: ia64
host: ia64-suse-linux-gnu
build: ia64-suse-linux-gnu
target: ia64-suse-linux-gnu
configured with: ../configure --enable-threads=posix --enable-long-long --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,f77,objc,java --with-gxx-include-dir=/usr/include/g++ --enable-nls --with-slibdir=/lib --enable-shared ia64-suse-linux
>Description:
#include __FILE__ does not work.
>How-To-Repeat:
$ cat file.c
#define PASS 1
#if PASS == 1
#undef PASS
#define PASS 2
#include __FILE__
#undef PASS
#define PASS 3
#include __FILE__
#endif
PASS
$ gcc -E file.c
file.c:5:18: file.c__: No such file or directory
file.c:8:18: file.c__: Success
# 10 "file.c"
3
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-19 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 7:16 Andreas Schwab [this message]
2001-06-19 8:07 neil
2001-06-19 8:09 neil
2001-06-21 13:46 Neil Booth
2001-06-21 14:04 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=200106191414.f5JEERe08361@D65.suse.de \
--to=schwab@suse.de \
--cc=gcc-gnats@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).