public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbrandmeyer at earthlink dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/13675] New: #including a precompiled header more than once in the same unit fails
Date: Wed, 14 Jan 2004 03:10:00 -0000 [thread overview]
Message-ID: <20040114031017.13675.jbrandmeyer@earthlink.net> (raw)
This has also been observed on powerpc-apple-darwin6.8 with current sources as
of 1pm US Eastern time today when configured with ../gcc/configure
--enable-languages=c,c++ --program-suffix=-3.4
--enable-version-specific-runtime-libs
Both the C and C++ compilers are affected.
If a header file is precompiled and #included more than once in the same
compilation unit, the second inclusion generates an error like
"filename:linenumber:columnnumber calling fdopen: Bad file descriptor"
Consider this trivial example:
-----------pch-header.h-------
#ifndef PCH_HEADER_TEST_H
#define PCH_HEADER_TEST_H
extern int i;
#endif
----------another-pch-user.h-------
#include "pch-header.h"
----------pch-user1.cpp-------
#include "pch-header.h"
#include "another-pch-user.h"
---------------end----------
$ g++-3.4 -c -o pch-header.h.gch pch-header.h
$ g++-3.4 -c -o pch-user1.o pch-user1.cpp
In file included from pch-user1.cpp:2:
another-pch-user.h:1:24: calling fdopen: Bad file descriptor
$ g++-3.4 -v
Reading specs from /home/jonathan/lib/gcc/i686-pc-linux-gnu/3.4.0/specs
Configured with: ../gcc/configure --enable-languages=c,c++ --program-suffix=-3.4
--disable-checking --prefix=/home/jonathan
Thread model: posix
gcc version 3.4.0 20040108 (experimental)
--
Summary: #including a precompiled header more than once in the
same unit fails
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: pch
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jbrandmeyer at earthlink dot net
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13675
next reply other threads:[~2004-01-14 3:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 3:10 jbrandmeyer at earthlink dot net [this message]
2004-01-14 12:29 ` [Bug pch/13675] " rwgk at yahoo dot com
2004-01-15 2:00 ` geoffk at gcc dot gnu dot org
2004-04-17 0:43 ` geoffk at gcc dot gnu dot org
2004-04-17 5:13 ` geoffk at gcc dot gnu dot org
2004-04-17 5:22 ` jbrandmeyer at earthlink dot net
2004-04-17 9:29 ` geoffk at gcc dot gnu dot org
2004-04-17 10:41 ` geoffk at gcc dot gnu dot org
2004-04-17 12:40 ` geoffk at gcc dot gnu dot org
2004-04-24 19:09 ` pinskia at gcc dot gnu dot org
2004-04-24 20:45 ` v13 at it dot teithe dot gr
2004-06-03 3:55 ` pegasus at ifdo dot pugmarks dot com
2004-06-25 22:02 ` geoffk at gcc dot gnu dot org
2005-09-22 10:54 ` a dot darovskikh at compassplus dot ru
2005-09-23 12:45 ` pinskia at gcc dot gnu dot org
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=20040114031017.13675.jbrandmeyer@earthlink.net \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).