From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 19D79385828E; Wed, 1 May 2024 23:00:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 19D79385828E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714604431; bh=+3MDfU13YIzeh2vqUmI3NRnUl35lwKFExs9tmk/Wzgs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BTM1rkftCJgXV29ljlBj29CvliotscfP9V1ywubXPp3e4fGVwgqu7B4PPo2vqj/fS FDRszjoiQPGSpjdIqkOURNRilJdLmRrsZD6XdKY4qdSChub39PyYwOydmRpoYXgzXW 0H6/9kcenxNZkl/GMOMc5hnpbxPwxd/XfKNJ30qw= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114913] "verify_gimple failed" due to addition of two constexpr strings Date: Wed, 01 May 2024 23:00:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: ice-checking, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114913 --- Comment #5 from Andrew Pinski --- (In reply to Jorg Brown from comment #4)=20 > Also odd is that the above code (including a()) works fine on gcc 10.1 > through 13.2. As seen https://godbolt.org/z/z3qnosG37 This is not really odd since it does fail with those compilers with -fcheck= ing (which is the default for the GCC trunk development). It also works with the trunk (in this case) with -fno-checking . Basically GCC has some internal checks to make sure things internally are consistent but they are failing in this case and you can turn them off/on at compile time.=