From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9B2253858D39; Wed, 12 Apr 2023 06:05:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9B2253858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681279502; bh=IsPYwIBaqDWubNPKHmbRdZmvU8ThNGzpK2MUsISwUgk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TjW11W6SJnjhj26arDti7WzVe5czGCYCypvaOEoHraJl9WpP23wBqlgXqAq8IpoQW sdbmeo03qVtgx8usiEbxIC1xr6JD56ieNdt9h7PVX37Iw2IZJWaYl31XdNrJJm22Nv 3I4HBKvvQzrG9LKu4nh+zWoAhA9J57AkIUTT1B7s= From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109477] [13 regression] ICE: internal compiler error: verify_flow_info failed (error: returns_twice call is not first in basic block 8) when building busybox Date: Wed, 12 Apr 2023 06:05:02 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amonakov at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: resolution cc bug_status 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=3D109477 Alexander Monakov changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |amonakov at gcc dot gnu.org Status|UNCONFIRMED |RESOLVED --- Comment #4 from Alexander Monakov --- This is also SLP emitting a vector ctor in an unexpected place, just like in PR109469, so I'll go ahead and mark it as a dup. Thanks for the report. *** This bug has been marked as a duplicate of bug 109469 ***=