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 EF1BB3858C54; Wed,  5 Apr 2023 01:06:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF1BB3858C54
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1680656774;
	bh=3c0AS7OwsBebc/GtUyM2izzk21L89OvsDzWcz1RXsq8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=y7LfJ44eZ0uSczBtLLoSJPxwLb7mF6G326y4PjOuJPOUaezB2TnkNDpOvSP0z812V
	 UxWoXEVOR6NVhxDDhXAM1DIdg9ag1EwLFDKfr8vEvaplS6kFW8s5Um04hG2Zneyk1L
	 s5MbRlMVlxWwe2Tpvsg1aYBbkDNXkzDZ2X/O6YbE=
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109137] [12 regression] Compiling ffmpeg with -m32 on
 x86_64-pc-linux-gnu hangs on libavcodec/h264_cabac.c since
 r12-9086-g489c81db7d4f75
Date: Wed, 05 Apr 2023 01:06:04 +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.0
X-Bugzilla-Keywords: compile-time-hog, ice-on-invalid-code, inline-asm
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sjames at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109137-4-li9jpC6SbI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109137-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=3D109137

--- Comment #24 from Sam James <sjames at gcc dot gnu.org> ---
As a heavy consumer of the branch for our distribution, I'd say it was a (n=
ice)
surprise, but then I wasn't expecting it to end up exposing a latent bug (or
making it worse).

At the end of the day, not much harm done in this case, as we noticed it pr=
etty
quickly. glibc also tends to backport tuning improvements (often more invas=
ive
than this) which is also sometimes a bit controversial.=