> > That was really just a suggestion by a user. > But yeah, your toolchain somewhat works.
It's great to know it doesn't just work on my machine :) strdup is not mapped to msvcrt._strdup I know how to fix this it has to do with adding extra objects for aliases to libmsvcrt.a Support just need to be added to genlib for COFF SPEC Weak Externals 4.5.3 Auxiliry Format 3 -mwindows, -mconsole and likely also -mdll are not supported yet (there's > this wclang project on github that hacks around it) the linker accepts a min of ld and link arguments "-subsystem:console" "-subsystem:windows" should work for this. I have currently only added the ones I needed as alias's to lld. It should take a whole of 30 seconds to add the 3 above. I'll send you an updated patch for this soon. no binutils, dlltool and such, I mean everything mingw-w64 would bring you > except ld which is now lld, right... llvm provides most of what we need already except for resource handling example: objdump -> llvm-objdump dlltool is replaced by a new tool in mingw-w64 called genlib no complete build instructions, really, I have no idea how to build my own > toolchain :) > the instructions in the source archive you gave me only got me a clang > toolchain... https://github.com/Alexpux/MSYS2-packages/blob/master/mingw-w64-cross-crt-git/PKGBUILD I assume you are only missing the steps to build the crt with clang and genlib, here is an example of how that is done. This only works on windows hosts atm because of a bug in llvm that I am investigating. llvm-ar cru destroys the libs genlib creates when appending objects on a non windows host it seems. Installing the headers is done as normal. Anyway, I managed to build some easy parts of the Wine testsuite with it > already, so hey, Awesome! > Keep up the great work and merry xmas! Nice :) We are getting places then, you too mate :) PS: Next target will be AArch64 ;) no, really, I figure this will be much > bigger in the M$ world than ARM32... Should be easy as genlib already supports aarch64, I also have llvm-objdump recognizing aarch64 objects. I have done all this work in a way so that as soon as MS or some other llvm engineer adds support for MSVC aarch64, I can just add compiler support for mingw-w64 with just a few small patches. :) This was one of my goals for this, so we can piggy back in future and never fall behind and new windows target. We will still need to put in the assembly work on the mingw-w64 side but that seems to be something you do very early on because of wine :) On Thu, Dec 24, 2015 at 9:54 AM, André Hentschel <[email protected]> wrote: > Am 24.12.2015 um 07:36 schrieb Martell Malone: > > [PATCH] CRT_fp10: Protect ARM implementation against compiler > optimizations > > > > I take it the clang based toolchain I sent you works ? > > I'm going to move onto fixing i686 and then do a personal builds release > for xmas. > > That was really just a suggestion by a user. > But yeah, your toolchain somewhat works. > Minor issues so far: > strdup is not mapped to msvcrt._strdup > -mwindows, -mconsole and likely also -mdll are not supported yet > (there's this wclang project on github that hacks around it) > no binutils, dlltool and such, I mean everything mingw-w64 would > bring you except ld which is now lld, right... > no complete build instructions, really, I have no idea how to > build my own toolchain :) > the instructions in the source archive you gave me only > got me a clang toolchain... > > > Anyway, I managed to build some easy parts of the Wine testsuite with it > already, so hey, Awesome! > Keep up the great work and merry xmas! > > PS: Next target will be AArch64 ;) no, really, I figure this will be much > bigger in the M$ world than ARM32... >
------------------------------------------------------------------------------
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
