public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/16465] gfortran does not accept -ffixed-line-length-72 Date: Sat, 10 Jul 2004 12:54:00 -0000 [thread overview] Message-ID: <20040710125440.10489.qmail@sourceware.org> (raw) In-Reply-To: <20040710125253.16465.billingd@gcc.gnu.org> ------- Additional Comments From billingd at gcc dot gnu dot org 2004-07-10 12:54 ------- Cut and paste error. Does not accept -ffixed-line-length-72 error is: f951: warning: unknown register name: line-length-72 -- What |Removed |Added ---------------------------------------------------------------------------- Summary|gfortran does not accept - |gfortran does not accept - |ffixed-line-length-72.f |ffixed-line-length-72 Target Milestone|--- |3.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16465
next prev parent reply other threads:[~2004-07-10 12:54 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-10 12:52 [Bug fortran/16465] New: gfortran does not accept -ffixed-line-length-72.f billingd at gcc dot gnu dot org 2004-07-10 12:54 ` billingd at gcc dot gnu dot org [this message] 2004-07-11 12:31 ` [Bug fortran/16465] gfortran does not accept -ffixed-line-length-72 tobi at gcc dot gnu dot org 2004-07-12 4:53 ` pinskia at gcc dot gnu dot org 2004-07-17 18:28 ` pinskia at gcc dot gnu dot org 2004-07-18 13:00 ` cvs-commit at gcc dot gnu dot org 2004-07-18 13:06 ` cvs-commit at gcc dot gnu dot org 2004-07-18 13:09 ` [Bug fortran/16465] parser chokes with ffixed-line-length-7 tobi at gcc dot gnu dot org 2004-07-22 17:59 ` tow21 at cam dot ac dot uk 2004-09-01 14:39 ` tobi at gcc dot gnu dot org 2005-01-06 14:40 ` tobi 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=20040710125440.10489.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).