On Apr 11, 5:13 pm, Cactus <rieman...@googlemail.com> wrote:
> On Apr 11, 2:06 am, Nicholas Kinar <n.ki...@usask.ca> wrote:
>
> > 157 tests:
> >          2 failed to build
> >          118 ran correctly
> >          37 failed
> > .. completed - press ENTER
>
> I can't explain the two that failed to build but I also find the 37
> test failures, which means that something has changed since I last
> built the win32 version.
>
> Sadly I don't often build this version as I am running only x64 code
> now (all tests pass on x64).
>
> So I have no idea where the problem lies - I have had a quick look but
> there is nothing obvious wrong.
>
> Interestingly all the tests pass for both win32 and x64 using Visual
> Studio 2010.
>
> I doubt that I can offer you a solution as it will be unproductive
> from my point of view to spend time debugging win32 code - especially
> so since it works in win32 using Visual Studio 2010.

Although I still cannot explain the two build failures, the 37 test
failures have shown up a bug in the Visual Studio 2008 compiler.

If you disable optimisation for the file mul.c (right click on the
file in the IDE and look in the C++ properties dialogue under the
Optimisation item, select 'disabled' in the Optimisation box) all
tests should then pass (at least the do for me).

It seems that a change in mul.c has triggered a VC++ bug (not present
in Visual Studio 2010).

    Brian

-- 
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 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.

Reply via email to