From: JonY <10walls@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: introduce --enable-mingw-full32 to default to --large-address-aware
Date: Tue, 09 Oct 2018 11:31:00 -0000 [thread overview]
Message-ID: <18c16bb7-c54f-f086-0e90-f06345be10d8@gmail.com> (raw)
In-Reply-To: <or1s8zww9k.fsf@lxoliva.fsfla.org>
[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]
On 10/09/2018 04:59 AM, Alexandre Oliva wrote:
> On Oct 5, 2018, Joseph Myers <joseph@codesourcery.com> wrote:
>
>> A new configure option needs documenting in install.texi.
>
> Ah, yes, thanks for the reminder.
>
> On Oct 6, 2018, JonY <10walls@gmail.com> wrote:
>
>> They're both OK as far as I can see. I just don't like the configure
>> name implying all 32bit pointers are used by userspace. Perhaps just
>> --enable-large-address-aware?
>
> That might suggest the flag affects all targets, including Cygwin, so
> I'm following the existing (undocumented) practice in suggesting
> --enable-mingw-large-address-aware instead. Please let me know if you'd
> rather not have mingw in the option name, and for it to affect (in the
> --disable form) the Cygwin target as well.
>
It is fine to turn it on by default in 32bit MinGW (i686-*-mingw*), but
leave the defaults as is for others like Cygwin, I am not too sure of
the effects for Cygwin.
I don't think mingw should be in the configure name as this is
applicable to all Win32 PE targets, it is a PE flag after all.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-09 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 6:48 Alexandre Oliva
2018-10-05 16:40 ` Joseph Myers
2018-10-09 6:38 ` Alexandre Oliva
2018-10-09 11:31 ` JonY [this message]
2018-10-10 4:58 ` Alexandre Oliva
2018-10-10 5:20 ` JonY
2018-10-10 8:00 ` Alexandre Oliva
2018-10-11 0:18 ` JonY
2018-10-11 7:46 ` NightStrike
2018-10-11 11:32 ` JonY
2018-10-12 6:28 ` Alexandre Oliva
2018-10-12 11:27 ` JonY
[not found] ` <ork1lxspuw.fsf@lxoliva.fsfla.org>
2018-11-01 10:48 ` JonY
2018-11-07 11:59 ` Alexandre Oliva
2018-11-07 12:50 ` JonY
2018-11-08 9:45 ` Alexandre Oliva
2018-11-08 15:39 ` JonY
2018-11-09 10:49 ` Alexandre Oliva
2018-11-09 12:22 ` JonY
2018-10-07 8:03 ` JonY
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=18c16bb7-c54f-f086-0e90-f06345be10d8@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=oliva@adacore.com \
/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).