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 E031938582B1; Wed,  6 Dec 2023 07:59:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E031938582B1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701849571;
	bh=HyzdpRM61v9D67NUP/mwWAxVApyc/Ke3uPmxZ5KBYlo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=d5J7j2T9WOEdvPk1WlwQDu9ucjkY0ddYm9cgRfb+rbPvZA+Atay96Uoj67IqBto0K
	 /dnHQ1trubjUzawBpi74Z9StJesAUED/PgkJx3vxbjnLNj4IbxWYkZDOUHv2CCCYPb
	 7og9iL7qnLjI8+reNSU9037RVQSWI3QWaGDsGhwM=
From: "rguenth 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: Wed, 06 Dec 2023 07:59:31 +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: rguenth 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-112868-4-cTpADzPPyD@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 #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
The behavior shouldn't change dependent on --enable-checking.  Can't we make
sure to pass -mno-any (if that exists...) during bootstrap and testsuite
instead?=