public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi 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: Wed, 24 May 2023 10:06:45 +0000	[thread overview]
Message-ID: <bug-109954-4-J0z53V5UO9@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 #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
How about:

--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -34089,7 +34089,9 @@ on x86-64 processors in 64-bit environments.
 Generate code for a 16-bit, 32-bit or 64-bit environment.
 The @option{-m32} option sets @code{int}, @code{long}, and pointer types
 to 32 bits, and
-generates code that runs on any i386 system.
+generates code that runs in 32-bit mode. N.B., using @option{-march} might
+be required to produce code suitable for a specific CPU family, e.g.,
+@option{-march=i486}.

 The @option{-m64} option sets @code{int} to 32 bits and @code{long} and
pointer
 types to 64 bits, and generates code for the x86-64 architecture.

  parent reply	other threads:[~2023-05-24 10:06 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 [this message]
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
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-J0z53V5UO9@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).