public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40647] 32-bit pointers on 64-bit operating systems
Date: Sat, 04 Jul 2009 19:03:00 -0000 [thread overview]
Message-ID: <20090704190303.10160.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40647-10391@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
------- Comment #9 from hjl dot tools at gmail dot com 2009-07-04 19:03 -------
/Qauto-ilp32 (-auto-ilp32): Specifies that the application cannot exceed
a 32-bit address space, which allows the compiler to use 32-bit pointers
whenever possible.
To use this option, you must also specify /Qipo [value] (-
ipo[value]). Using the ¨Cauto-ilp32 option on programs that can
exceed 32-bit address space (2**32) may cause unpredictable
results during program execution. This option has no effect on
systems with Intel 64 unless the /QaxP (-axP), /QxP (-xP),
/QaxT (-axT), or /QxT (-xT) option is also used.
Note: For IA-32 processors, this option is not supported
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40647
next prev parent reply other threads:[~2009-07-04 19:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 10:03 [Bug target/40647] New: " tkoenig at gcc dot gnu dot org
2009-07-04 10:07 ` [Bug target/40647] " dominiq at lps dot ens dot fr
2009-07-04 10:16 ` tkoenig at gcc dot gnu dot org
2009-07-04 11:02 ` rguenth at gcc dot gnu dot org
2009-07-04 11:34 ` tkoenig at gcc dot gnu dot org
2009-07-04 11:55 ` joseph at codesourcery dot com
2009-07-04 13:50 ` rguenth at gcc dot gnu dot org
2009-07-04 18:56 ` hjl dot tools at gmail dot com
2009-07-04 19:00 ` pinskia at gcc dot gnu dot org
2009-07-04 19:03 ` hjl dot tools at gmail dot com [this message]
2009-07-04 19:18 ` rguenth at gcc dot gnu dot 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=20090704190303.10160.qmail@sourceware.org \
--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).