It doesn't work because FreeBSD 8.0 uses a broken binutils that doesn't have lahf/sahf , the only fix is to upgrade. However , we didn't have this before because that particular file was assembled with our internal yasm and not an external gas? , the change is because I never got around to converting the new assembler to yasm format. I will convert this file now.
Jason On Monday 09 November 2009 09:38:21 Bill Hart wrote: > Thanks for the report Case. > > I'll add a ticket for the lahf, sahf issue. I assume the machine was > the same, i.e. an AMD64 and not an old Pentium 4. > > A fix isn't jumping out at me, but I am sure it won't be difficult to > provide one. We'll try and do that before the final release. > > Bill. > > 2009/11/9 casevh <cas...@gmail.com>: > > Hi, > > > > I was testing mpir 1.3.0rc2 and gmpy on FreeBSD 8.0 RC2 AMD64. I > > tracked down a gmpy error to a change in behavior in mpf_set_str: it > > returns an error when passed the string "3.400e+00" but "3.400e+0" is > > accepted. > > > > Both strings are accepted on Windows with mpir-1.3.0rc1. I haven't > > tested Linux yet. > > > > Notes on FreeBSD 8.0: By default, it uses an old version of binutils > > and GCC 4.2.1. Compilation failed with > > > > tmp-addlsh_n.s:75: Error: suffix or operands invalid for 'sahf' > > tmp-addlsh_n.s:85: Error: suffix or operands invalid for 'lahf' > > > > I compiled (via ports) the current version of binutils and GCC 4.4. > > MPIR compiles and tests successfully with this combination. > > > > Case > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
