From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2BF433858D37; Tue, 27 Feb 2024 20:54:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BF433858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709067285; bh=F/saW8kajW7k1eGZLw1g80XmtI+/4JslREHAqeGjHsI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=t+2cqo8ufXZyNDGlAOVnv7mRqigH/uSbj4P3FS/UWO1TGxNck66aA9bG2UH/ySaLd IH/4OUd1ieg/egEleWeUmF6YYbbwTdMdMWnHkOajEfgsZyEWV0LwOIgNPPupVYaufp b7FXhhq/lb3M3AEF6hXnV0CXDuAlPDS4qEWk2B/Y= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112868] GCC passes -many to the assembler for --enable-checking=release builds Date: Tue, 27 Feb 2024 20:54:44 +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: bug_status assigned_to Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112868 Peter Bergner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |jeevitha at gcc dot= gnu.org --- Comment #6 from Peter Bergner --- (In reply to Sam James from comment #4) > I was quite surprised by this behaviour. It should really be documented if > we're going to stick with it, but I don't think we should at all.. I have asked Jeevitha to prepare a patch to remove the -many assembler opti= on usage on --enable-checking=3Drelease builds. It would be nice if we can get some distro help to do some practice distro builds using the patch to verify whether there it causes any fallout on dis= tro builds to help decide whether we should push the patch or leave things as t= hey are.=