public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje 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: Tue, 05 Dec 2023 22:51:06 +0000	[thread overview]
Message-ID: <bug-112868-4-R249ecEaMc@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 #2 from David Edelsohn <dje at gcc dot gnu.org> ---
Narrowing the ISA dialect range accepted by the assembler is good in theory to
catch problems.  We need to ensure that this doesn't break a lot of existing
code and make POWER more tedious.

Most people want to download a pre-built package.  If someone downloads source
code, they want it to configure, build and run without problems.

While this change will ensure that new packages are more strictly conformant
and may not cause problems with new Linux distro releases, it could prevent
older packages from building with newer releases of GCC.

  parent reply	other threads:[~2023-12-05 22:51 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 [this message]
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
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-R249ecEaMc@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).