From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D8DC93858436; Wed, 22 Mar 2023 09:59:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D8DC93858436 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679479170; bh=29KrN5wzlKA+9vze4ANMh6P7wrZEIvjIm6l+HNTDaZg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LAGpFpt/dTRZXJ5HDVmSHSzeIjC5LFURbkEzbI9P1ffte3zpUgHg7+BVqj25CeL3E NAI70lgYcdcETR+HbVJJDYWdZSVEf+pNQtgXVEL62nCb9Nw2L65KYiPtIYucjUzHZD WILnnIb5aaYG/4+QgUqq+MzlRV0cR4x1vwDuX1So= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/109237] csmith: another timeout with -g -O3 this time since r12-156-g8d4c374c4419a875 Date: Wed, 22 Mar 2023 09:59:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: compile-time-hog, needs-reduction X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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=3D109237 --- Comment #10 from Richard Biener --- There's similar issues with GIMPLE uses of last_stmt () which generally (but not always) want to look at a possible control transfer stmt. It looks like we're not guaranteed to have no debug stmts after such, in particular CFG cleanup seems to be ready to remove debug stmts after a noreturn call. But GIMPLE verify_flow_info should already choke on that, so it might be only a temporary thing to accept?=