public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/28528] [4.0/4.1/4.2 regression] Trouble compiling header files with "-x c++" using g++ Date: Mon, 21 Aug 2006 23:22:00 -0000 [thread overview] Message-ID: <20060821232200.19887.qmail@sourceware.org> (raw) In-Reply-To: <bug-28528-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from geoffk at gcc dot gnu dot org 2006-08-21 23:22 ------- The same thing happens if you use 'file.i' rather than 'file.h': it gets treated as preprocessed rather than C++ source: $ ./g++ -B./ -c -x c++ file.i -### Reading specs from ./specs Target: i386-apple-darwin9.0.0d2 Configured with: /Volumes/Data/co/gcc-trunk/configure Thread model: posix gcc version 4.2.0 20060818 (experimental) "./cc1plus" "-fpreprocessed" "file.i" "-fPIC" "-quiet" "-dumpbase" "file.i" "-mtune=i386" "-auxbase" "file" "-o" "/var/tmp//ccztNIJB.s" "./as" "-arch" "i386" "-force_cpusubtype_ALL" "-o" "file.o" "/var/tmp//ccztNIJB.s" If someone has a built FSF 3.3 around, it would be good if they could check whether this behaviour persists there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28528
next prev parent reply other threads:[~2006-08-21 23:22 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-28 13:42 [Bug driver/28528] New: " reichelt at gcc dot gnu dot org 2006-07-28 14:18 ` [Bug driver/28528] " pinskia at gcc dot gnu dot org 2006-07-29 5:27 ` pinskia at gcc dot gnu dot org 2006-07-31 23:39 ` mmitchel at gcc dot gnu dot org 2006-08-18 4:07 ` pinskia at gcc dot gnu dot org 2006-08-18 4:48 ` dannysmith at users dot sourceforge dot net 2006-08-18 4:52 ` pinskia at gcc dot gnu dot org 2006-08-21 21:20 ` janis at gcc dot gnu dot org 2006-08-21 23:22 ` geoffk at gcc dot gnu dot org [this message] 2006-08-21 23:27 ` [Bug driver/28528] [4.0/4.1/4.2 Regression] C language extensions override -x in C++ driver pinskia at gcc dot gnu dot org 2006-08-21 23:34 ` janis at gcc dot gnu dot org 2006-08-24 0:20 ` patchapp at dberlin dot org 2006-08-25 0:24 ` dannysmith at gcc dot gnu dot org 2006-08-25 0:27 ` [Bug driver/28528] [4.0/4.1 " dannysmith at users dot sourceforge dot net 2007-02-03 18:40 ` gdr at gcc dot gnu dot org 2007-02-03 20:43 ` pinskia at gcc dot gnu dot org 2007-02-14 9:14 ` mmitchel at gcc dot gnu dot org 2008-07-04 15:46 ` [Bug driver/28528] [4.1 " jsm28 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=20060821232200.19887.qmail@sourceware.org \ --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: 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).