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 B3D11385EC09; Mon,  6 May 2024 16:46:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B3D11385EC09
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715013979;
	bh=T0aVykUU815LNrDFzHbu+LvreJy4PAVsp6haIggYqy0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DFlONyaChu4AHh5e5pAGZhmIvN8E8V4EeuLUAKWXfUMg69qdAsSJcY03osManZIe6
	 mZmbAPYrdxSqThF4e73SvAR46NIkadG8sdrVeFjAeoUb61G4hTKaPQlhKphinODavR
	 dXr2/2YzFjFiWsWMgaRamtjZ4Vtlp1Yc734mLu8U=
From: "nisse at lysator dot liu.se" <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 16:46:18 +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: nisse at lysator dot liu.se
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-T9wQHkRqKe@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 #13 from Niels M=C3=B6ller <nisse at lysator dot liu.se> ---
(In reply to Peter Bergner from comment #11)

> This is clearly a stage1 patch, so we'll wait until
> then before submitting it.

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 (accordin=
g to
https://gcc.gnu.org/develop.html#timeline, gcc-14 stage1 ended several mont=
hs
ago), it will have to wait for gcc-15?=