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/23862] Select Fortran source form appropriately for "-pipe" Date: Wed, 21 Jun 2006 11:37:00 -0000 [thread overview] Message-ID: <20060621111444.13746.qmail@sourceware.org> (raw) In-Reply-To: <bug-23862-9019@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from fxcoudert at gcc dot gnu dot org 2006-06-21 11:14 ------- I'm rediscovering that bug, so I'm assigning this bug to myself in order to not forget it again :) One remark: I don't understand exactly why the second part would be needed: -{"@f95", "%{!E:f951 %i %(cc1_options) %{J*} %{I*}\ +{"@f95", "%{!E:f951 %i %{!ffixed-form:-ffree-form} %(cc1_options) %{J*} %{I*}\ %{!fsyntax-only:%(invoke_as)}}", 0, 0, 0}, as currently, the @f95 sources (files with .f95 and .f90) are compiled correctly. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |fxcoudert at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Known to fail| |4.1.2 4.2.0 Last reconfirmed|2005-12-15 05:03:07 |2006-06-21 11:14:44 date| | Target Milestone|--- |4.1.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23862
next parent reply other threads:[~2006-06-21 11:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23862-9019@http.gcc.gnu.org/bugzilla/> 2006-06-21 11:37 ` fxcoudert at gcc dot gnu dot org [this message] 2006-06-24 16:21 ` fxcoudert at gcc dot gnu dot org 2006-07-02 21:17 ` [Bug fortran/23862] [4.1 only] " fxcoudert at gcc dot gnu dot org 2006-07-02 21:22 ` [Bug fortran/23862] " fxcoudert at gcc dot gnu dot org 2005-09-13 16:05 [Bug fortran/23862] New: " macro at linux-mips dot org 2005-09-13 16:06 ` [Bug fortran/23862] " macro at linux-mips dot org 2005-09-13 20:03 ` 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=20060621111444.13746.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).