Windows breakage -- again
mp2e at archlinux.us
Thu Jul 17 06:36:55 UTC 2014
i686 has been out for so long that worrying about i386 support is silly.
MinGW-w64 uses i686 by default. Even i586 is *incredibly* conservative.
On Jul 16, 2014 11:34 PM, "Johan Tibell" <johan.tibell at gmail.com> wrote:
> A perhaps silly question, *should* ghc-prim be built with i386 or i686?
> On Thu, Jul 17, 2014 at 8:33 AM, Niklas Larsson <metaniklas at gmail.com>
> > I just found exactly the same thing! Well, I used i686 instead.
> > Sounds like it's worthwhile to see if this is limited to ghc-prim or if
> > there's more stuff that's built with i386.
> > 2014-07-17 8:21 GMT+02:00 Páli Gábor János <pali.gabor at gmail.com>:
> >> 2014-07-17 0:51 GMT+02:00 Páli Gábor János <pali.gabor at gmail.com>:
> >> > 2014-07-17 0:47 GMT+02:00 Niklas Larsson <metaniklas at gmail.com>:
> >> >> I hope they can just be done away with at the source, that is to make
> >> >> gcc
> >> >> generate the assembly primitives. GHC should already be built with
> >> >> i686, but
> >> >> does that reach ghc-prim?
> >> >
> >> > This depends on GCC -- if no -march=XXX is explicitly set, I guess it
> >> > will take its default, which may vary platform by platform.
> >> All right, I have finally got a Windows (x64) machine and installed
> >> the msys2 environment by the GHC wiki . This has GCC 4.5.2 (as
> >> Niklas wrote earlier), where the default -march is i386. You should
> >> see this line when trying to compile Johan's test program with the -v
> >> flag set:
> >> COLLECT_GCC_OPTIONS= ... '-v' '-mtune=i386' '-march=i386'
> >> With the -march=i586 flag explicitly set in the command line, no
> >> __sync_fetch_and_add_n() calls are generated.
> >> 
> ghc-devs mailing list
> ghc-devs at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs