From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A656E3857C4F; Thu, 24 Sep 2020 06:44:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A656E3857C4F From: "jeremy at jeremysanders dot net" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 10.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jeremy at jeremysanders dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2020 06:44:13 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D97176 --- Comment #3 from Jeremy Sanders --- 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 t= his 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-conformi= ng code. Its use is only intended as a short-term fix for non-standard code." ?=