public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments Date: Tue, 17 Sep 2002 12:26:00 -0000 [thread overview] Message-ID: <20020917192600.25913.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/7947; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> Cc: neil@gcc.gnu.org, bug-hurd@gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/7947: cpp0 -std=gnu99 rejects # comments Date: Tue, 17 Sep 2002 20:22:38 +0100 Marcus Brinkmann wrote:- > That is my fault for not being precise enough in my bug report, sorry. > > The problem is that gcc calls the preprocessor with this ordering when > compiling an assembler file (foo.S) with the -std=gnu99 option. > > Try "echo \# foo > foo.S" and "gcc -std=gnu99 -o foo foo.S", this triggers > the bug. -v shows that gcc passes -std=gnu99 to cpp when preprocessing the > file. Right, but everything you state is intentional. -lang-asm deliberately comes first, otherwise it would clobber various other flags the user may have passed, such as -fdollars-in-identifiers, -trigraphs etc. The problem you have is that -std=gnu99 applies to the C language, and not to assembler. What is the reason you need to pass the switch? If it's to avoid a spurious warning, we may be able to disable the warning if -lang-asm. If it's to achieve some additional functionality, we may be able to retain that functionality if -lang-asm. Neil.
next reply other threads:[~2002-09-17 19:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-17 12:26 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-17 12:46 Marcus Brinkmann 2002-09-17 11:56 Marcus Brinkmann 2002-09-17 11:22 neil 2002-09-17 6:36 marcus
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=20020917192600.25913.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --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: 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).