public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109954] x86-64's -m32 does not conform to documentation
Date: Fri, 02 Jun 2023 08:41:45 +0000	[thread overview]
Message-ID: <bug-109954-4-lM2GAVbegN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109954-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109954

--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
i386 is an overloaded term, sometimes it means just i386 CPUs and not i486 and
later,
at other times it means the all CPUs capable of running i386 32-bit code,
sometimes it means ia32.
I don't think it would be a good idea to change the defaults, that would do
more harm than good and all users can pick their own defaults if they don't
like the defaults.

  parent reply	other threads:[~2023-06-02  8:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  9:33 [Bug target/109954] New: " jbeulich at suse dot com
2023-05-24  9:45 ` [Bug target/109954] " redi at gcc dot gnu.org
2023-05-24  9:53 ` jakub at gcc dot gnu.org
2023-05-24  9:58 ` jbeulich at suse dot com
2023-05-24 10:02 ` redi at gcc dot gnu.org
2023-05-24 10:05 ` jakub at gcc dot gnu.org
2023-05-24 10:06 ` redi at gcc dot gnu.org
2023-05-24 10:09 ` jakub at gcc dot gnu.org
2023-05-24 10:11 ` redi at gcc dot gnu.org
2023-05-25  7:41 ` rguenth at gcc dot gnu.org
2023-06-01 10:39 ` redi at gcc dot gnu.org
2023-06-01 11:01 ` cvs-commit at gcc dot gnu.org
2023-06-01 12:01 ` cvs-commit at gcc dot gnu.org
2023-06-01 12:01 ` cvs-commit at gcc dot gnu.org
2023-06-01 12:02 ` cvs-commit at gcc dot gnu.org
2023-06-01 12:03 ` cvs-commit at gcc dot gnu.org
2023-06-01 12:03 ` redi at gcc dot gnu.org
2023-06-02  8:37 ` tschwinge at gcc dot gnu.org
2023-06-02  8:41 ` jakub at gcc dot gnu.org [this message]
2023-06-02  8:49 ` jbeulich at suse dot com
2023-06-02  8:50 ` arsen at gcc dot gnu.org
2023-07-10  5:10 ` pinskia 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-109954-4-lM2GAVbegN@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).