public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36376] -cpp -save-temps passes unknown options to f951 Date: Tue, 09 Dec 2008 19:55:00 -0000 [thread overview] Message-ID: <20081209195430.7603.qmail@sourceware.org> (raw) In-Reply-To: <bug-36376-13648@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from dfranke at gcc dot gnu dot org 2008-12-09 19:54 ------- Subject: Bug 36376 Author: dfranke Date: Tue Dec 9 19:53:02 2008 New Revision: 142608 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142608 Log: 2008-12-09 Daniel Franke <franke.daniel@gmail.com> PR fortran/36376 PR fortran/37468 * lang-specs.h: Pass on -i* options to f951 to (probably) report them as unknown. Duplicate gcc.c (cpp_options), but omit -fpch-preprocess on -save-temps. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/lang-specs.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36376
next prev parent reply other threads:[~2008-12-09 19:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-29 18:37 [Bug fortran/36376] New: " dfranke at gcc dot gnu dot org 2008-06-07 8:31 ` [Bug fortran/36376] " dfranke at gcc dot gnu dot org 2008-12-09 19:55 ` dfranke at gcc dot gnu dot org [this message] 2008-12-09 19:58 ` dfranke 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=20081209195430.7603.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).