public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames 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: Sun, 03 Mar 2024 23:47:46 +0000 [thread overview]
Message-ID: <bug-112868-4-ioi4nXeJxG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112868-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112868
--- Comment #9 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Jeevitha from comment #8)
> Created attachment 57584 [details]
> Removed -many from the options passed by default to the assembler.
>
> Sam James, can you do a practice distro build using this patch?
Hi Jeevitha, I've added this to our patchset tonight and asked some people to
give it a spin on top of that too.
next prev parent reply other threads:[~2024-03-03 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 18:27 [Bug target/112868] New: " bergner at gcc dot gnu.org
2023-12-05 18:29 ` [Bug target/112868] " bergner at gcc dot gnu.org
2023-12-05 22:51 ` dje at gcc dot gnu.org
2023-12-06 7:59 ` rguenth at gcc dot gnu.org
2023-12-06 8:37 ` sjames at gcc dot gnu.org
2023-12-08 0:13 ` bergner at gcc dot gnu.org
2024-02-27 20:54 ` bergner at gcc dot gnu.org
2024-02-28 15:38 ` sjames at gcc dot gnu.org
2024-03-01 12:09 ` jeevitha at gcc dot gnu.org
2024-03-03 23:47 ` sjames at gcc dot gnu.org [this message]
2024-04-08 9:19 ` sjames at gcc dot gnu.org
2024-04-08 21:52 ` bergner at gcc dot gnu.org
2024-04-22 20:00 ` pinskia at gcc dot gnu.org
2024-05-06 16:46 ` nisse at lysator dot liu.se
2024-05-06 20:23 ` bergner at gcc dot gnu.org
2024-05-07 15:03 ` jeevitha at linux dot ibm.com
2024-05-09 11:27 ` sjames at gcc dot gnu.org
2024-05-19 21:10 ` sjames at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112868-4-ioi4nXeJxG@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).