public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/18452] Fortran options induces warning for fortran that needs preprocessing Date: Wed, 02 Nov 2005 21:57:00 -0000 [thread overview] Message-ID: <20051102215742.17505.qmail@sourceware.org> (raw) In-Reply-To: <bug-18452-10259@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from fxcoudert at gcc dot gnu dot org 2005-11-02 21:57 ------- Subject: Bug 18452 Author: fxcoudert Date: Wed Nov 2 21:57:35 2005 New Revision: 106402 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106402 Log: PR fortran/18452 * lang-specs.h: Pass -lang-fortran to the preprocessor. * gcc/c.opt: Add a -lang-fortran option. * gcc/c-opts.c: Add a lang_fortran flag. (c_common_init_options): Handling the -lang-fortran option. (c_common_handle_option): Add a case for Fortran options in preprocessing. Remove cases for -ffixed-form and -ffixed-line-length. Add a case for -lang-fortran. Modified: branches/gcc-4_0-branch/gcc/ChangeLog branches/gcc-4_0-branch/gcc/c-opts.c branches/gcc-4_0-branch/gcc/c.opt branches/gcc-4_0-branch/gcc/fortran/ChangeLog branches/gcc-4_0-branch/gcc/fortran/lang-specs.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18452
next prev parent reply other threads:[~2005-11-02 21:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18452-10259@http.gcc.gnu.org/bugzilla/> 2005-10-13 7:50 ` c dot lemmen at fz-juelich dot de 2005-11-02 21:57 ` fxcoudert at gcc dot gnu dot org [this message] 2005-11-04 8:29 ` fxcoudert at gcc dot gnu dot org 2005-11-04 8:31 ` fxcoudert at gcc dot gnu dot org 2004-11-12 15:15 [Bug fortran/18452] New: -fno-second-underscore induces warning coudert at clipper dot ens dot fr 2005-08-01 13:16 ` [Bug fortran/18452] Fortran options induces warning for fortran that needs preprocessing pinskia at gcc dot gnu dot org 2005-08-23 15:07 ` 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=20051102215742.17505.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).