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 5E9F53858414; Fri, 14 Apr 2023 13:15:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5E9F53858414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1681478145;
	bh=89PF/1NmNbjvzZQF4UnBNiPsEFxatUUllE7WVsSPDpg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wvLUHHbwrtgt4kKidXx2LR8tZZekTuk9piGahYy7IHgr84HQkkVJ010FusPojevs6
	 bhhBvaRdkUaA65gVw6qLRejntm4Qmd9z6GaAeb5anMKr0vxnGARg+yrbVC1YC2r02U
	 u3hlufR0Wep1VNagje1XiZ433yzA3WGvMadRNsDE=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109491] [11/12 Regression] Segfault in
 tree-ssa-sccvn.cc:expressions_equal_p()
Date: Fri, 14 Apr 2023 13:15:44 +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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109491-4-HCJp9N7Pnr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109491-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=3D109491

--- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> ---
Just to make the point, for the testcase when compiling with -O -g I see

> grep 'INLINE_ENTRY' t.ii.031t.einline | wc -l=20
16976
> grep 'INLINE_ENTRY' t.ii.034t.ccp1 | wc -l
15530
> grep 'INLINE_ENTRY' t.ii.043t.cddce1 | wc -l
14180

so there's some (not the majority) of inlined bodies removed by the first
constant propagation pass and more at the end of the early optimization
phase.  It's a bit unreliable since not all inlines result in a INLINE_ENTRY
debug stmt.  It also shows this likely isn't the biggest issue.

A factor of two compared to clang can be easily attributed to bigger
IL representation as well.

For me the testcase with -O2 builds in 17s with release checking enabled
so that's not too bad (on a fast x86 machine).  The most expensive pass
is RTL PRE, accounting for 1/4 of the compile-time.  With -O3 it's even
faster.

With -Dalways_inline=3Duser the compile time reduces to 3s though.=