From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id B52BC384241C; Thu,  2 Jul 2020 15:31:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B52BC384241C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1593703897;
 bh=lNwBAexQ60vYapZzD4hyMzH8OFb59YjADsUYkFxvvQo=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=Aq+CGS2V9Lm+TurhvtE4C2TfN2qsPzBYr3SiupHzuSyDYNreKUWqftkOFM9n28Hrm
 zA3oJKrlXg2anQ77q8WPbpISWZ0rJfTDCSxo/psi07wWo+j0v2V26G7Hx3PGL2KCbr
 NYeZSvkJwtwEoqUOAiTShJxhSZ380aXNYr0U1ND0=
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52279] Fortran translation issues
Date: Thu, 02 Jul 2020 15:31:37 +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: 4.7.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-52279-4-iRvhwA4i3M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2020 15:31:37 -0000

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

--- Comment #6 from kargl at gcc dot gnu.org ---
(In reply to markeggleston from comment #5)
> (In reply to markeggleston from comment #4)
> > Regarding comment 2.
> >=20
> > Using -fallow-invalid-boz results in an ICE. I'll create a new PR.
>=20
> Not true, tried it on the wrong file and jumped to the wrong conclusion.

This is wrong.

index 26ea01f..8ecf4ff 100644 (file)
--- a/gcc/fortran/check.c
+++ b/gcc/fortran/check.c
@@ -67,7 +67,7 @@ gfc_invalid_boz (const char *msg, locus *loc)
       return false;
     }

-  const char hint[] =3D " [see %<-fno-allow-invalid-boz%>]";
+  const char *hint =3D " [see %<-fno-allow-invalid-boz%>]";
   size_t len =3D strlen (msg) + strlen (hint) + 1;
   char *msg2 =3D (char *) alloca (len);
   strcpy (msg2, msg);

There is no -fno-allow-invalid-boz option.  The option is
-fallow-invalid-boz.  fortan/lang.opt defines the options
with the RejectNegative annotation.=