On 11/09/2018 10:48 AM, Alexandre Oliva wrote:
> On Nov 8, 2018, JonY <10wa...@gmail.com> wrote:
>
>> No, no. By quick I just mean using -Wl,--large-address-aware on an
>> existing gcc install, nothing complex. Sorry about not making it clear.
>
> Ah, good!
>
>> I now understand the problem,
On Nov 8, 2018, JonY <10wa...@gmail.com> wrote:
> No, no. By quick I just mean using -Wl,--large-address-aware on an
> existing gcc install, nothing complex. Sorry about not making it clear.
Ah, good!
> I now understand the problem, thanks for the clarification about the
> patch. Patch is OK.
On 11/08/2018 09:45 AM, Alexandre Oliva wrote:
> On Nov 7, 2018, JonY <10wa...@gmail.com> wrote:
>
>> On 11/07/2018 08:34 AM, Alexandre Oliva wrote:
>>> On Nov 1, 2018, JonY wrote:
>>>
Looks like it causes an error on 64bit:
/usr/libexec/gcc/x86_64-w64-mingw32/ld: unrecognized option
On Nov 7, 2018, JonY <10wa...@gmail.com> wrote:
> On 11/07/2018 08:34 AM, Alexandre Oliva wrote:
>> On Nov 1, 2018, JonY wrote:
>>
>>> Looks like it causes an error on 64bit:
>>> /usr/libexec/gcc/x86_64-w64-mingw32/ld: unrecognized option
>>> '--large-address-aware'
>>
>> What does? The
On 11/07/2018 08:34 AM, Alexandre Oliva wrote:
> On Nov 1, 2018, JonY wrote:
>
>> Looks like it causes an error on 64bit:
>> /usr/libexec/gcc/x86_64-w64-mingw32/ld: unrecognized option
>> '--large-address-aware'
>
> What does? The patch I suggested? The current trunk?
>
> What was the
On Nov 1, 2018, JonY <10wa...@gmail.com> wrote:
> Looks like it causes an error on 64bit:
> /usr/libexec/gcc/x86_64-w64-mingw32/ld: unrecognized option
> '--large-address-aware'
What does? The patch I suggested? The current trunk?
What was the command in this case? How was the toolchain
On 10/31/2018 10:39 PM, Alexandre Oliva wrote:
> On Oct 12, 2018, Alexandre Oliva wrote:
>
>> * config/i386/mingw32.h (LINK_SPEC_LARGE_ADDR_AWARE): Define,
>> based on MINGW_DEFAULT_LARGE_ADDR_AWARE.
>> (LINK_SPEC): Insert it.
>> * config/i386/mingw-264.h: Likewise.
>
On Oct 12, 2018, Alexandre Oliva wrote:
> * config/i386/mingw32.h (LINK_SPEC_LARGE_ADDR_AWARE): Define,
> based on MINGW_DEFAULT_LARGE_ADDR_AWARE.
> (LINK_SPEC): Insert it.
> * config/i386/mingw-264.h: Likewise.
^ s/2/w/, fixing...
Now, it
On 10/12/2018 05:56 AM, Alexandre Oliva wrote:
> On Oct 11, 2018, JonY <10wa...@gmail.com> wrote:
>
>> On 10/11/2018 02:57 AM, NightStrike wrote:
>>>
>>> Except that options typically don't get removed, just deprecated. It
>>> seems cleaner to me to drop mingw from the name and make it default
On Oct 11, 2018, JonY <10wa...@gmail.com> wrote:
> On 10/11/2018 02:57 AM, NightStrike wrote:
>>
>> Except that options typically don't get removed, just deprecated. It
>> seems cleaner to me to drop mingw from the name and make it default to
>> enabled for cygwin.
> It is already enabled for
On 10/11/2018 02:57 AM, NightStrike wrote:
>
> Except that options typically don't get removed, just deprecated. It
> seems cleaner to me to drop mingw from the name and make it default to
> enabled for cygwin.
>
It is already enabled for Cygwin, but good point,
--enable-large-address-aware it
On Wed, Oct 10, 2018 at 7:37 PM JonY <10wa...@gmail.com> wrote:
>
> On 10/10/2018 04:58 AM, Alexandre Oliva wrote:
> > On Oct 10, 2018, JonY <10wa...@gmail.com> wrote:
> >
> >> On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
> >>> On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
> >
> >>> Now, if
On 10/10/2018 04:58 AM, Alexandre Oliva wrote:
> On Oct 10, 2018, JonY <10wa...@gmail.com> wrote:
>
>> On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
>>> On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
>
>>> Now, if you wish it to affect Cygwin as well, I could implement that,
>>> and drop
On Oct 10, 2018, JonY <10wa...@gmail.com> wrote:
> On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
>> On Oct 9, 2018, JonY <10wa...@gmail.com> wrote:
>> 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
On 10/10/2018 03:24 AM, Alexandre Oliva wrote:
> On Oct 9, 2018, JonY <10wa...@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
On Oct 9, 2018, JonY <10wa...@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
On 10/09/2018 04:59 AM, Alexandre Oliva wrote:
> On Oct 5, 2018, Joseph Myers wrote:
>
>> A new configure option needs documenting in install.texi.
>
> Ah, yes, thanks for the reminder.
>
> On Oct 6, 2018, JonY <10wa...@gmail.com> wrote:
>
>> They're both OK as far as I can see. I just
On Oct 5, 2018, Joseph Myers wrote:
> A new configure option needs documenting in install.texi.
Ah, yes, thanks for the reminder.
On Oct 6, 2018, JonY <10wa...@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
On 10/05/2018 02:18 AM, Alexandre Oliva wrote:
> Add a configure knob for mingw32 and 64 toolchains to default passing
> --large-address-aware to the linker, when creating 32-bit binaries.
> -Wl,--disable-large-address-aware can still reverse its effects.
>
> I've tested this with cross
A new configure option needs documenting in install.texi.
--
Joseph S. Myers
jos...@codesourcery.com
Add a configure knob for mingw32 and 64 toolchains to default passing
--large-address-aware to the linker, when creating 32-bit binaries.
-Wl,--disable-large-address-aware can still reverse its effects.
I've tested this with cross i686-pc-mingw32-gcc and
x86_64-w64-mingw64-gcc (is this the usual
21 matches
Mail list logo
