On Saturday 17 July 2010 15:17:41 Cactus wrote: > On Jul 17, 1:44 pm, Jason <[email protected]> wrote: > > On Saturday 17 July 2010 14:45:30 Cactus wrote: > > > On Jul 17, 2:28 pm, Bill Hart <[email protected]> wrote: > > > > Does this use Linux calling conventions or C calling conventions? > > > > The > > > > > > problem is, on Windows 64 the assembly code usually needs to be > > > > specially written to support the correct calling conventions. > > > > > > > > This has been done for the MSVC build, but I don't know how > > > > MinGW-64 > > > > > > handles this, and we certainly didn't do anything to configure to fix > > > > this yet. So at present, you get much, much better performance > > > > from > > > > > > the MSVC build, I think. > > > > > > > > I also personally had problems getting MinGW-64 to work at all on > > > > my > > > > > > Windows 7 machine. These issues may have been fixed in the past > > > > few > > > > > > months though, as it has been a while since I tried. > > > > > > > > Bill. > > > > > > > > On 17 July 2010 14:23, degski <[email protected]> wrote: > > > > > Hi Jason, > > > > > > > > > >> If you want 64bit (which will be MUCH faster) then use MSVC if > > > > you can > > > > > > >> , we do support the free download version > > > > > > > > > > I'm not claiming MPIR compiles correctly (haven't tried compiling > > > > > MPIR, but was able to compile various other libs correctly), but > > > > > MinGW-w64 - for 64 bit Windows now exists. > > > > > > > > > >http://sourceforge.net/projects/mingw-w64/ > > > > > > > > > > Cheers > > > > > > > > > > degski > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the > > > > Google > > > > > > > Groups "mpir-devel" group. To post to this group, send email to > > > > > [email protected]. To unsubscribe from this group, > > > > send > > > > > > > email to [email protected]. For more > > > > options, > > > > > > > visit this group athttp://groups.google.com/group/mpir- > > > > devel?hl=en.- > > > > > > > Hide quoted text - > > > > > > > > - Show quoted text - > > > > > > I have used mingw64 to compile the generic C versions of both GMP > > > > and > > > > > MPIR on Windows x64 and it works fine. Mingw64 uses the correct > > > Windows calling conventions and it can hence work with YASM > > > > assembler > > > > > code in Windows format. > > > > > > In prinnciple it could hence use our Windows assembler code but it > > > would have to be set up to do this and this would require someone to > > > do it. > > > > Should be easy to do > > > > > Brian- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - > > I agree - but I am not volunteering as I have enough to do with the VC+ > + builds :-) >
I might give it a go > As an aside I should also mention that, in repairing a documentation > bug in the YASM description of the Windows calling conventions for > Peter Johnson, I discoverd that I am being overly restrictive in the > format of our Windows assembler code in one respect - a function can > have multiple epilogues. This will make some conversions a bit easier. > > The use of 64-bit integers for x64 mpn integer parameters on x64 also > allowed the removal of 32 to 64 bit register extension, which is a > further simplification. > > Brian I might try a few conversions myself , could be good practise . -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
