public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus at oberhumer dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/17361] New: gcc driver complains about C++ options when assembling Date: Wed, 08 Sep 2004 21:33:00 -0000 [thread overview] Message-ID: <20040908213338.17361.markus@oberhumer.com> (raw) gcc has always ignored C/C++ options when assembling, but apparently some new checks for explicit C++ options do not follow this principle. > touch a.s b.S > gcc-2.95 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S > g++-2.95 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S > gcc-3.2 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S > g++-3.2 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S > gcc-3.4 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for C > g++-3.4 -Wall -fno-rtti -fomit-frame-pointer -c a.s b.S cc1: warning: command line option "-fno-rtti" is valid for C++/ObjC++ but not for C -- Summary: gcc driver complains about C++ options when assembling Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: driver AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: markus at oberhumer dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17361
next reply other threads:[~2004-09-08 21:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-08 21:33 markus at oberhumer dot com [this message] 2004-09-09 3:13 ` [Bug other/17361] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-10-11 17:13 ` [Bug other/17361] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org 2004-10-11 22:57 ` cvs-commit at gcc dot gnu dot org 2004-10-11 23:02 ` [Bug other/17361] [3.3/3.4 " pinskia at gcc dot gnu dot org 2004-10-14 21:43 ` cvs-commit at gcc dot gnu dot org 2004-10-14 21:46 ` [Bug other/17361] [3.3 " pinskia at gcc dot gnu dot org 2005-01-21 2:02 ` markus at oberhumer dot com 2005-04-30 13:54 ` gdr 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=20040908213338.17361.markus@oberhumer.com \ --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).