Oh sorry, I mean the ones listed on Minh's test page. Not these ones.
I haven't looked at the sextus failure yet.
Bill.
On 27 May 2010 21:29, Jason Moxham wrote:
> On Thursday 27 May 2010 21:17:07 Bill Hart wrote:
>> The gcc 4.3.2 test failures are all expected. Nothing we can do about
>> that.
On Thursday 27 May 2010 21:17:07 Bill Hart wrote:
> The gcc 4.3.2 test failures are all expected. Nothing we can do about
> that. That's a compiler bug. GMP and MPIR both simply won't build
> correctly with that version of gcc.
>
> Bill.
yes , but that has nothing to do with these failures?
[jaso
The gcc 4.3.2 test failures are all expected. Nothing we can do about
that. That's a compiler bug. GMP and MPIR both simply won't build
correctly with that version of gcc.
Bill.
On 27 May 2010 20:56, Jason Moxham wrote:
> This maybe related or not
>
> PASS: t-dc_bdiv_qr_n
> PASS: t-dc_bdiv_qr
>
On May 27, 8:55 pm, "Chris Saunders" wrote:
> From my message:
>
> >> > First line of the Build "Output" window:
>
> >> > 1>-- Build started: Project: lib_mpir_nehalem, Configuration: Debug
> >> > Win32 --
>
> Does this not mean that I was attempting a Win32 build?
Yes this is a win32 b
From my message:
> First line of the Build "Output" window:
> 1>-- Build started: Project: lib_mpir_nehalem, Configuration: Debug
> Win32 --
Does this not mean that I was attempting a Win32 build?
Regards
Chris Saunders
--
From: "Cact
This maybe related or not
PASS: t-dc_bdiv_qr_n
PASS: t-dc_bdiv_qr
PASS: t-dc_bdiv_q
inv_divappr_q.c:45: GNU MP assertion failed: dn >= 6
/bin/sh: line 4: 24955 Aborted (core dumped) ${dir}$tst
FAIL: t-gcdext
PASS: st_fat
PASS: st_instrument
=
The iras failure is my test script fault
gcc-4.5.0 has a ICE when used at -O3 so in the mpir configure mechanism if we
are on itanium then we choose -O2 , this works when we build with
nothing
--build=ia64-*
--build=none-unknown-linux-gnu
but NOT when
--build=long-unknown-linux-gnu
--build=longl
I'll have to take a look. It is surely a bug in the test code. Though,
given the absolutely enormous amount of testing I did with gcdext, I
am finding it hard to believe that a segfault can still be in there.
It must somehow have to do with the change we made the other day.
Bill.
On 27 May 2010 2
Hi Jason,
On Fri, May 28, 2010 at 4:58 AM, Jason Moxham wrote:
> Thanks , go ahead
Done.
--
Regards
Minh Van Nguyen
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubs
our svn with the gcdext test changes still fail on sextus.skynet
PASS: t-sb_bdiv_qr
PASS: t-dc_bdiv_q_n
PASS: t-dc_bdiv_qr_n
PASS: t-dc_bdiv_qr
PASS: t-dc_bdiv_q
/bin/sh: line 4: 18644 Segmentation fault ${dir}$tst
FAIL: t-gcdext
PASS: st_fat
PASS: st_instrument
=
On Thursday 27 May 2010 16:04:38 Minh Nguyen wrote:
> Hi folks,
>
> At this wiki page [1] is the build and test results on over 24
> machines of various hardware/platform combinations. Unfortunately, on
> about 8 of these machines, you find that MPIR r2978 builds fine, make
> check passes, make tun
> It shouldn't be necessary but I have added x64 configurations to the
> pre-build steps to see if it solves your problem.
Hi,
That works for me now and all tests pass OK. I don't know why we see
different behavior. Anyway. Thanks.
Regards,
Chris
--
You received this message because you are s
On Wed, May 26, 2010 at 3:00 AM, Minh Nguyen wrote:
> MPIR 2.1.0-rc1 was released on 25th May 2010.
Mac OSX test results:
- OSX Leopard - gcc version 4.0.1 (Apple Inc. build 5493) - 64bit Core2
All tests passed
- OSX Leopard - gcc version 4.0.1 (Apple Inc. build 5493) - 32bit Core2
All tests p
Hi folks,
At this wiki page [1] is the build and test results on over 24
machines of various hardware/platform combinations. Unfortunately, on
about 8 of these machines, you find that MPIR r2978 builds fine, make
check passes, make tune completes successfully, and the test suite
pass. The other ma
On May 27, 3:03 pm, Cactus wrote:
> On May 27, 2:46 pm, chrmhoffmann wrote:
>
>
>
>
>
> > Hi again,
>
> > I am now trying to compile with win x64 and I have problems doing
> > that. With the native x64 compiler I am running into a problem with
> > the TRACKER.
> > The error message is:
> > 1>--
On May 27, 2:46 pm, chrmhoffmann wrote:
> Hi again,
>
> I am now trying to compile with win x64 and I have problems doing
> that. With the native x64 compiler I am running into a problem with
> the TRACKER.
> The error message is:
> 1>-- Build started: Project: gen-mpir, Configuration: Debug
On May 27, 2:38 pm, chrmhoffmann wrote:
> > Ok, I've made a change to vsyasm.props in the MPIR repository that
> > adds the ability to override the default vsyasm path.
>
> > If the environment variable YASMPATH is set to the directory
> > (including the final backslash) where vsyasm is located,
Hi again,
I am now trying to compile with win x64 and I have problems doing
that. With the native x64 compiler I am running into a problem with
the TRACKER.
The error message is:
1>-- Build started: Project: gen-mpir, Configuration: Debug Win32
--
1>Build started 5/27/2010 3:45:07 PM.
1>In
> Ok, I've made a change to vsyasm.props in the MPIR repository that
> adds the ability to override the default vsyasm path.
>
> If the environment variable YASMPATH is set to the directory
> (including the final backslash) where vsyasm is located, this will
> override the default vsyasm location.
On May 27, 11:22 am, Cactus wrote:
> On May 27, 10:13 am, chrmhoffmann wrote:
>
> > Hi,
>
> > I am building with vs2010 and the build works fine. I have just a
> > question regarding the vsyasm.exe. I don't really like the idea that I
> > have to put the vsyasm.exe in the visual studio installa
On May 27, 10:13 am, chrmhoffmann wrote:
> Hi,
>
> I am building with vs2010 and the build works fine. I have just a
> question regarding the vsyasm.exe. I don't really like the idea that I
> have to put the vsyasm.exe in the visual studio installation path.
> Can't the solution just pick whatev
Hi,
I am building with vs2010 and the build works fine. I have just a
question regarding the vsyasm.exe. I don't really like the idea that I
have to put the vsyasm.exe in the visual studio installation path.
Can't the solution just pick whatever vsyasm.exe that is in the PATH?
Or at least have it
22 matches
Mail list logo
