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 E55843858425; Sat, 25 Nov 2023 13:31:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E55843858425
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700919087;
	bh=VXKQYM7zVkUzkvHC0Ws1GFijXxFJ/G2zwbrvQ3lMInE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hiGP4tIBokakdx5TJw7qJbCo6OC9daoshOCGy/dUfTYwO9G4IQ6PAv45WPtxCIMrb
	 vyGRBXipxYw1cOnwra9UJ9AgGUeU9wo/3fXDqaRcRAnYha+ocnEGNzDh415GwFlnxs
	 895TM6yXjAXZGgXvB6pkf9bA3v7fQJCggr8DFgZk=
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109811] libjxl 0.7 is a lot slower in GCC 13.1 vs Clang
 16
Date: Sat, 25 Nov 2023 13:31:26 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.1.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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: <bug-109811-4-YBOrAKmXhU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109811-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=3D109811

--- Comment #18 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I made a typo:

Mainline with -O2 -flto  -march=3Dnative run manually since build machinery=
 patch
is needed
        23.03
        22.85
        23.04

Should be=20
Mainline with -O3 -flto  -march=3Dnative run manually since build machinery=
 patch
is needed
        23.03
        22.85
        23.04

So with -O2 we still get slightly lower score than clang with -O3 we are
slightly better. push_back inlining does not seem to be a problem (as teste=
d by
increasing limits) so perhaps more agressive unrolling/vectorization settin=
gs
clang has at -O2.

I think upstream jpegxl should use -O3 or -Ofast instead of -O2.  It is qui=
te
typical kind of task that benefits from large optimization levels.

I filled in https://github.com/libjxl/libjxl/issues/2970=