public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108369] FM509 Fails to compile with error
Date: Fri, 13 Jan 2023 15:29:24 +0000 [thread overview]
Message-ID: <bug-108369-4-0pqt1Y3KPT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108369-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #12 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, Jan 13, 2023 at 11:49:44AM +0000, ben.brewer at codethink dot co.uk
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
>
> --- Comment #11 from Ben Brewer <ben.brewer at codethink dot co.uk> ---
> So I was using "-x f77" which I would expect to instruct the compiler to run in
> a mode compatible with Fortran 77, it seems non-intuitive to have to enable
> -std=legacy to compile the very tests which define f77.
>
gfortran started life as a Fortran 95 compiler with a bunch of
extensions. The -x f77 option might be a relic from g77 and
only effects whether one has fixed source form code or free
source form code. "f77" appears twice in gcc.info under the
description of the -x option. The meaning of "-x f77" isn't
actually documented.
To set the Fortran standard conformance, use the -std option (e.g.,
-std=legacy, -std=f95, -std=f2003, -std=f2008, -std=f2018). There
isn't an -std=f77, If one is compiling old code, it is recommended
to use -std=legacy to turn off a bunch of warning/errors.
next prev parent reply other threads:[~2023-01-13 15:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 13:32 [Bug fortran/108369] New: " ben.brewer at codethink dot co.uk
2023-01-11 19:57 ` [Bug fortran/108369] " anlauf at gcc dot gnu.org
2023-01-11 21:38 ` kargl at gcc dot gnu.org
2023-01-11 21:50 ` kargl at gcc dot gnu.org
2023-01-12 17:59 ` sgk at troutmask dot apl.washington.edu
2023-01-13 0:17 ` jvdelisle at gcc dot gnu.org
2023-01-13 1:09 ` jvdelisle at gcc dot gnu.org
2023-01-13 1:20 ` jvdelisle at gcc dot gnu.org
2023-01-13 1:21 ` jvdelisle at gcc dot gnu.org
2023-01-13 1:22 ` jvdelisle at gcc dot gnu.org
2023-01-13 2:55 ` sgk at troutmask dot apl.washington.edu
2023-01-13 11:49 ` ben.brewer at codethink dot co.uk
2023-01-13 15:29 ` sgk at troutmask dot apl.washington.edu [this message]
2023-01-13 17:06 ` jvdelisle at gcc dot gnu.org
2023-01-13 20:15 ` jvdelisle at gcc dot gnu.org
2023-01-19 1:15 ` jvdelisle at gcc dot gnu.org
2023-03-18 16:05 ` [Bug fortran/108369] FM509 Fails to compile with error when using undocumented -x option jvdelisle at gcc dot gnu.org
2023-03-18 18:22 ` anlauf at gcc dot gnu.org
2023-03-18 23:55 ` jvdelisle at gcc dot gnu.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=bug-108369-4-0pqt1Y3KPT@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).