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 89C603858D39; Mon,  6 May 2024 20:23:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89C603858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715027021;
	bh=rvs+g4RaiRjUNQHAUpC1CHlGktSX2uE3N48qzEAH78o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TNu9EO96cfj9uAZMnA6OmlMXBQ7gAEBdq/iH8Equitag4RIBFiBihFAolpwMP3YE1
	 vp00fez4FxfFbbktjx1TW59kFJPU0wiYe8SJO6rwZCVrB48yFxrDMngZWCqBZRuct+
	 54MMRq+efOO56tpH7zwkk1Bxh5Vu56z1UJSqe/Eg=
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112868] GCC passes -many to the assembler for
 --enable-checking=release builds
Date: Mon, 06 May 2024 20:23:40 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jeevitha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-112868-4-CMhOuUHa5e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112868-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=3D112868

--- Comment #14 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Niels M=C3=B6ller from comment #13)
> I'm not that familiar with gcc development procedures. Do I understand you
> correctly, that a fix for this bug will not be included in gcc-14 (accord=
ing
> to https://gcc.gnu.org/develop.html#timeline, gcc-14 stage1 ended several
> months ago), it will have to wait for gcc-15?

Correct, I meant waiting for GCC 15 stage1.  I want it to burn-in on trunk =
for
a long while, because it had the potential to disrupt distro package builds=
.=20
It seems clean so far with the practice Gentoo builds, but I'll feel more
comfortable when other distros start using it too.=20

That said, Jeevitha, now that we're in stage1, can you please post your pat=
ch?=