public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeremy at jeremysanders dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97176] Cannot return deferred length strings when using -fno-automatic
Date: Thu, 24 Sep 2020 06:44:13 +0000	[thread overview]
Message-ID: <bug-97176-4-2eqfCSL1MU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97176-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97176

--- Comment #3 from Jeremy Sanders <jeremy at jeremysanders dot net> ---
I'm not using -fno-automatic out of choice, unfortunately (I'd never use it
otherwise). I maintaining part of a large software package which has this
switched on (for unclear reasons). It will require some testing to remove this
option.

What would be really useful is a warning in the manual which makes it clear
that it is a bad idea to use this option. This would help prevent people
switching it on without knowing that it breaks standards-conforming code.
Unless you know the fortran standard well, it just seems a minor code
generation option from the current docs. I'd be happy if this bug was closed
with a documentation update (or a warning is added for this case).

What about adding something like

"Use of this option is highly discouraged as it can break standard-conforming
code. Its use is only intended as a short-term fix for non-standard code."

?

  parent reply	other threads:[~2020-09-24  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 10:01 [Bug fortran/97176] New: " jeremy at jeremysanders dot net
2020-09-23 16:43 ` [Bug fortran/97176] " kargl at gcc dot gnu.org
2020-09-23 19:35 ` anlauf at gcc dot gnu.org
2020-09-24  6:44 ` jeremy at jeremysanders dot net [this message]
2020-10-05 12:23 ` dominiq at lps dot ens.fr

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-97176-4-2eqfCSL1MU@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).