> The pseh lib is 32 bit only. seh on 64 bit is different and btw
> supported by gcc :)
I was hoping you'd say that. That means I don't have to try to change
any of it.
Thanks for the info.
dw
--
See everything from
The pseh lib is 32 bit only. seh on 64 bit is different and btw supported
by gcc :)
Am 12.07.2013 20:33 schrieb "dw" :
> I'm doing more work on the intrinsics. While checking to see what my
> changes will affect, I noticed that
> (mingw-w64-libraries\pseh\src\i386\framebased-gcchack.c) is using
>
I'm doing more work on the intrinsics. While checking to see what my
changes will affect, I noticed that
(mingw-w64-libraries\pseh\src\i386\framebased-gcchack.c) is using
__readfsdword and __writefsdword. These functions will gp fault if
called on x64.
Is this code intended to be x86 specifi
2013/7/11 dw :
> 1) Move these functions to intrin-impl.h:
>
> _InterlockedIncrement16, _InterlockedDecrement16,
> _InterlockedCompareExchange16, _InterlockedIncrement, _InterlockedDecrement,
> _InterlockedExchange, _InterlockedExchangeAdd, _InterlockedCompareExchange,
> _InterlockedIncrement64, _I
I think everyone's got their own build systems, LRN has one,
mingw-builds have theirs, Ruben has his, you've got yours (kudos for
using PowerShell though, I didn't know anyone did that ;-))
I wish I had the time to investigate porting either nix or homebrew to
Windows, but that'd just be another b
On Fri, 12 Jul 2013 19:43:04 +0200
Kai Tietz wrote:
> 2013/7/10 Jon :
> >> > > While the question about what current users are using is already hard
> >> > > to answer, there's IMO a bigger one: What _potential_ users are there
> >> > > that aren't already using mingw-w64 :) I started looking i
2013/7/10 Jon :
>> > > While the question about what current users are using is already hard to
>> > > answer, there's IMO a bigger one: What _potential_ users are there that
>> > > aren't already using mingw-w64 :) I started looking into mingw-w64 maybe
>> > > a year ago, only to find out that
On 7/11/2013 11:21 PM, xunxun wrote:
>
> -Wl,--large-address-aware is only for x86 target
>
>
>
Thank you. I've removed this option, since my target is x64, and the compile
completes successfully.
-David C.
--
See eve