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 C72683858D28; Tue, 24 Jan 2023 19:41:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C72683858D28
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674589291;
	bh=+XfC9Xok6dxATemACueYZy6PpLAVzJsoxv6p2Sjj9kg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Tbo7egUa3o1GfRCamXI9BL/o2IvtJI0oTBOE56zvJwQog395Xl3nzq1SWV02hjk9a
	 mcS/Gk2AqgmFn45pd+HhW5RUR1aNl/EJDxljjGVk/IUeHHa0f2/8YfggBoUOKMgPoY
	 zMrNYg90OOL6uMQbTUNjkNf1MG4qXBX1I7GPaZfE=
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108523] -O1 -fcode-hoisting causes long
 compilation time  ?
Date: Tue, 24 Jan 2023 19:41:31 +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: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: cc
Message-ID: <bug-108523-4-Yg2f6Oo8j2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108523-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108523-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
List-Id: <gcc-bugs.sourceware.org>

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

David Binderman <dcb314 at hotmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenther at suse dot de

--- Comment #8 from David Binderman <dcb314 at hotmail dot com> ---
Commit g:fd8dd6c0384969170e594be34da278a072d5eb76 dated 2022-11-29
looks to be the one that causes the bug.

fd8dd6c0384969170e594be34da278a072d5eb76 is the first bad commit
commit fd8dd6c0384969170e594be34da278a072d5eb76
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 29 12:56:22 2022 +0100


Over to Richard for their best advice.=