On Apr 10, 8:18 pm, Bill Hart wrote:
> 2009/4/11 mabshoff :
> >> Anyhow, make and make check now work fine on cato with pathcc.
>
> > Are the default flags still not using optimization?
>
> I don't understand the question.
>
> If gcc is used, it uses optimisation -O2. If pathscale is used it
2009/4/11 mabshoff :
>
>
>
> On Apr 10, 8:13 pm, Bill Hart wrote:
>> I've added support as per Mariah's recommendation in trunk. It only
>> supports ABI=64 not n32 so I've changed that to the first one tried
>> for that arch. I had to edit acinclude.m4 to make sure it excluded
>> pathcc from the
On Apr 10, 8:13 pm, Bill Hart wrote:
> I've added support as per Mariah's recommendation in trunk. It only
> supports ABI=64 not n32 so I've changed that to the first one tried
> for that arch. I had to edit acinclude.m4 to make sure it excluded
> pathcc from the list of compilers it tested to
I've added support as per Mariah's recommendation in trunk. It only
supports ABI=64 not n32 so I've changed that to the first one tried
for that arch. I had to edit acinclude.m4 to make sure it excluded
pathcc from the list of compilers it tested to see if it was a gcc
compiler, otherwise it just
make test maybe?
2009/4/11 Jason Moxham :
>
>
> We need to find a way to disable make install/check for yasm easily , so that
> we can upgrade yasm without hassle . Currently I disabled each Makefile.am in
> each src directory for the install , there was about 15 files , and for make
> check I th
We need to find a way to disable make install/check for yasm easily , so that
we can upgrade yasm without hassle . Currently I disabled each Makefile.am in
each src directory for the install , there was about 15 files , and for make
check I think there was another 20 or so , yuck.
Perhaps cha
This includes some updates we'd like to have. But I think we'll put
off the upgrade to 1.2.0, as we don't want to break anything now that
we are so close to a release.
Bill.
2009/4/11 mabshoff :
>
> By the way: Yasm 0.8 was released *today*, so we might want to upgrade
> for the next major relea
By the way: Yasm 0.8 was released *today*, so we might want to upgrade
for the next major release of MPIR anyway:
Changes from 0.7.2 to 0.8.0:
* Add TASM-like basic syntax and frontend (contributed by Samuel
Thibault).
* Add movbe instruction and CPU feature.
* Use UNIX (not Windows) path fun
On Apr 10, 5:39 pm, Bill Hart wrote:
> The yasm tests fail on so many systemss that I think we should work
> harder to disable them. They really aren't relevant to the MPIR
> library. Yasm itself works fine, whether or not the tests pass and the
> real test of that for us is whether the library
The yasm tests fail on so many systemss that I think we should work
harder to disable them. They really aren't relevant to the MPIR
library. Yasm itself works fine, whether or not the tests pass and the
real test of that for us is whether the library passes make check.
Bill.
2009/4/11 mabshoff :
oops, twenty minutes after I reported that there was no problem an
issue with "make check" for yasm on some Acer notebook popped up:
PASS: modules/parsers/nasm/tests/nasm_test.sh
Test nasm_test: W +0-1/1 0%
** W: orphanwarn did not match errors and warnings!
FAIL: modules/parsers/nasm/tests/worp
On Apr 8, 12:18 pm, Bill Hart wrote:
> Release candidate 8 is available. It changes from symlinks to creating
> libraries in GMP compatibility mode and the option has been changed
> from --enable-gmplink to --enable-gmpcompat.
Ok, I ran some more tests with Sage last night and from this end th
On Fri, Apr 10, 2009 at 3:28 PM, Bill Hart wrote:
> ld -v
>
> On my system it returns:
> GNU ld (GNU Binutils) 2.18.50.20080625
>
> Assuming it returns the same on yours, then I'm pretty sure that is
> not the cause of the trouble you originally reported.
Yes mine is identical.
> I'll consider
Thanks Jeff. This now agrees with what I am getting.
My guess is that we used a different autoconf to build the latest RC
and that deals correctly with Cygwin.
We'll keep an eye on this in future releases. I can check that Cygwin
works on my machine, for example.
Your config.guess script is cor
On Fri, Apr 10, 2009 at 4:36 AM, Bill Hart wrote:
> Hi Jeff. I didn't manage to reproduce the Cygwin32 issue with
> mpir-1.0, even with a core 2 build, yet. I'm going to try 0.9 now to
> see if an earlier version of 1.0 might have had the bug (which would
> presumably be present in 0.9).
I don'
Also no issues with 0.9. So I've drawn a blank on this one.
Bill.
2009/4/10 Bill Hart :
> Hi Jeff. I didn't manage to reproduce the Cygwin32 issue with
> mpir-1.0, even with a core 2 build, yet. I'm going to try 0.9 now to
> see if an earlier version of 1.0 might have had the bug (which would
>
Hi Jeff. I didn't manage to reproduce the Cygwin32 issue with
mpir-1.0, even with a core 2 build, yet. I'm going to try 0.9 now to
see if an earlier version of 1.0 might have had the bug (which would
presumably be present in 0.9).
Is there any chance you could check out trunk from svn:
http://mo
No problems. Glad to hear it is resolved!! We can resolve this ticket it looks.
Bill.
2009/4/10 Case Vanhorsen :
>
> On Thu, Apr 9, 2009 at 10:57 PM, Bill Hart
> wrote:
>>
>> No issues with a Core 2 build.
>>
>> I'll now try MPIR 1.0 and see if the issue occurs with that version
>> instead of
18 matches
Mail list logo
