From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4AD40388456C; Wed, 26 Oct 2022 19:21:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AD40388456C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666812076; bh=TcrK3EH27xlf1/bA76ZgTvxMGVXQAENPpZd1b9M84Ws=; h=From:To:Subject:Date:In-Reply-To:References:From; b=W4D6C9d15w6EBClcw/eU3pcMW3aWuPbeuaswvkq60CoHwDj3dX3i+sIIRasXHrPPp wyzgnhbOjDZZcfftJDi6E1HWimX6KW7ipSdyxhLL4gZbSGEXbUDk3zjW6Tcw+2w9rA culg88DTEe/v/xPLvhgrMDegaV2vyHPx+L7dXIco= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103413] [10/11/12/13 Regression] ICE: Invalid expression in gfc_element_size since r10-2083-g8dc63166e0b85954 Date: Wed, 26 Oct 2022 19:21:15 +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: 12.0 X-Bugzilla-Keywords: ice-on-invalid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103413 --- Comment #13 from anlauf at gcc dot gnu.org --- (In reply to Steve Kargl from comment #12) > > pr103413-boz.f90:4:6: > >=20 > > 4 | r =3D z'1234' > > | 1 > > Error: BOZ literal constant at (1) is neither a DATA statement value no= r an > > actual argument of INT/REAL/DBLE/CMPLX intrinsic subprogram [see > > '-fno-allow-invalid-boz'] >=20 > This I need to look up in F2023. The statement may be allowed > only in an initialization expression. Given that F2023 is not yet official, I'd say we defer that. Maybe open a new (Meta-)PR that collects or references the new features. Oh boy, there's still a lot of F2018 that needs implementing...=