From: Alexandre Oliva <oliva@adacore.com>
To: JonY <10walls@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: introduce --enable-mingw-full32 to default to --large-address-aware
Date: Wed, 10 Oct 2018 04:58:00 -0000 [thread overview]
Message-ID: <or1s8y32ni.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <18c16bb7-c54f-f086-0e90-f06345be10d8@gmail.com> (JonY's message of "Tue, 9 Oct 2018 09:51:57 +0000")
On Oct 9, 2018, JonY <10walls@gmail.com> wrote:
> 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.
Cygwin already has --large-address-aware enabled, without an option to
disable it. That makes sense, considering that Cygwin targets Unix
programs, unlikely to have Windows-specific pointer assumptions.
That's why I phrased the option, and implemented it, as specific to
mingw.
Now, if you wish it to affect Cygwin as well, I could implement that,
and drop -mingw from the option name. I'd retain the current defaults
of each target, unless there's a strong reason to change them.
--
Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo
Be the change, be Free! FSF Latin America board member
GNU Toolchain Engineer Free Software Evangelist
next prev parent reply other threads:[~2018-10-10 3:24 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
2018-10-10 4:58 ` Alexandre Oliva [this message]
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=or1s8y32ni.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).