I'll change the website and tested the fallbacks for the broken debian gcc-4.3.2
Brian , is there any msvc changes needed for the mpir-2.5.2 branch?
Jason
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-
On Sat, 9 Jun 2012 09:54:38 +0100
Jason Moxham wrote:
> On Sat, 9 Jun 2012 09:14:51 +0100
> Jason Moxham wrote:
>
> > This is based on the 2.5.1 branch
>
> Thanks Jason, I have just downloaded it and saw that it is a minor
> evolution of 2.5.1.
>
> I assume that when 2.5.1 was branched fro
On Sat, 9 Jun 2012 09:14:51 +0100
Jason Moxham wrote:
> This is based on the 2.5.1 branch
Thanks Jason, I have just downloaded it and saw that it is a minor
evolution of 2.5.1.
I assume that when 2.5.1 was branched from trunk, it worked on MSVC.
So what matters are any post release patches
On Sat, 9 Jun 2012 09:14:51 +0100
Jason Moxham wrote:
> This is based on the 2.5.1 branch
Thanks Jason, I have just downloaded it and saw that it is a minor
evolution of 2.5.1.
I assume that when 2.5.1 was branched from trunk, it worked on MSVC.
So what matters are any post release patches
This is based on the 2.5.1 branch
Jason
--
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
On Sat, 9 Jun 2012 08:32:32 +0100
Jason Moxham wrote:
> I'll change the website and tested the fallbacks for the broken
> debian gcc-4.3.2
>
> Brian , is there any msvc changes needed for the mpir-2.5.2 branch?
Is this our next release or one we have already issued?
I don't normally work from
I'll change the website and tested the fallbacks for the broken debian gcc-4.3.2
Brian , is there any msvc changes needed for the mpir-2.5.2 branch?
Jason
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-
Awesome.
We should change the website though which still says x86_64 only fails
for that compiler.
Bill.
On 9 June 2012 07:35, Jason Moxham wrote:
> Hi
>
> I believe it's all 64bit cpu's , but I have a proper test now (from the gcc
> bug tracker so we can just use that , rather than just exclu
Hi
I believe it's all 64bit cpu's , but I have a proper test now (from the gcc bug
tracker so we can just use that , rather than just exclude gcc-4.3.2 as some
gcc-4.3.2 have been patched
Jason
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
T
On 2 June 2012 20:00, Bill Hart wrote:
> The machine gcc63 on the build farm is an Ultrasparc T1. However for
> some reason it complains about the compiler gcc-4.3.2. I was under the
> impression that the problem was only on x86_64. If not, then perhaps
> the website should be updated.
It seems t
10 matches
Mail list logo
