On 01.04.2014 01:29, Bill Hart wrote:
Hi all,
By now everyone will have heard about Canonical's new product, called
Youbetcha, which claims to offer native support for Linux applications
in Windows *at native speed*.
Hmmm, I was expecting it to run applications *twice* as fast as on
native Li
On 01/04/2014 00:30, Bill Hart wrote:
> Tuning is certainly done. So now is as good a time as any I would say.
Done
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an
Tuning is certainly done. So now is as good a time as any I would say.
Bill.
On 1 April 2014 01:23, Brian Gladman wrote:
> On 31/03/2014 23:46, Jean-Pierre Flori wrote:
> > Playing with different arch choices, it seems that x86_64w/gmp-mparam.h
> > lacks a definition for FFT_N_NUM.
>
> There m
Hi all,
By now everyone will have heard about Canonical's new product, called
Youbetcha, which claims to offer native support for Linux applications in
Windows *at native speed*.
I wish this had come along earlier, since even yesterday (Monday), I was
spitting chips at the 45 minutes it takes jus
On 31/03/2014 23:46, Jean-Pierre Flori wrote:
> Playing with different arch choices, it seems that x86_64w/gmp-mparam.h
> lacks a definition for FFT_N_NUM.
There might be several like that in mpn/x86w and mpn/x86_64w because I
haven't copied over the tuning files from the equivalent GCC directorie
Indeed it does. I will commit one shortly. Just about done with another
commit.
Bill.
On 1 April 2014 00:46, Jean-Pierre Flori wrote:
> Playing with different arch choices, it seems that x86_64w/gmp-mparam.h
> lacks a definition for FFT_N_NUM.
>
--
You received this message because you are s
Playing with different arch choices, it seems that x86_64w/gmp-mparam.h
lacks a definition for FFT_N_NUM.
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mpir-dev
On Monday, March 31, 2014 11:49:38 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Monday, March 31, 2014 10:45:48 PM UTC+2, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Monday, March 31, 2014 10:27:01 PM UTC+2, Jean-Pierre Flori wrote:
>>>
>>>
>>> Testing now on Cygwin64 (in a 64 bit Windows 7 VM).
>>
On Monday, March 31, 2014 10:45:48 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Monday, March 31, 2014 10:27:01 PM UTC+2, Jean-Pierre Flori wrote:
>>
>>
>> Testing now on Cygwin64 (in a 64 bit Windows 7 VM).
>>
> Built fine there as well with and without C++ support.
>
> Now running the testsui
On Monday, March 31, 2014 10:27:01 PM UTC+2, Jean-Pierre Flori wrote:
>
>
> Testing now on Cygwin64 (in a 64 bit Windows 7 VM).
>
Built fine there as well with and without C++ support.
Now running the testsuite.
--
You received this message because you are subscribed to the Google Groups
"m
On Monday, March 31, 2014 9:41:27 PM UTC+2, Bill Hart wrote:
>
> OK, I've committed it now.
>
> Bill.
>
Works fine on Cygwin32 (in a 32bit Windows XP VM) with and without C+
bindings.
Testing now on Cygwin64 (in a 64 bit Windows 7 VM).
--
You received this message because you are subscribed
OK, I've committed it now.
Bill.
On 31 March 2014 21:39, Bill Hart wrote:
> Ok, I'll test MinGW and MinGW32 then.
>
> I'm just about to commit it, so if you could use my version built with my
> autotools, that would be great.
>
> Bill.
>
>
> On 31 March 2014 21:36, Jean-Pierre Flori wrote:
>
Ok, I'll test MinGW and MinGW32 then.
I'm just about to commit it, so if you could use my version built with my
autotools, that would be great.
Bill.
On 31 March 2014 21:36, Jean-Pierre Flori wrote:
>
>
> On Monday, March 31, 2014 9:30:26 PM UTC+2, Bill Hart wrote:
>>
>> How on earth did you
On Monday, March 31, 2014 9:30:26 PM UTC+2, Bill Hart wrote:
>
> How on earth did you test it so fast? It takes 45 minutes just to run
> configure on my machine!
>
Our mails crossed each other.
I'll be testing Cygwin and Cygwin64 now.
--
You received this message because you are subscribed t
On Monday, March 31, 2014 9:28:51 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Monday, March 31, 2014 9:20:51 PM UTC+2, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Monday, March 31, 2014 9:15:15 PM UTC+2, Jean-Pierre Flori wrote:
>>>
>>> Dear all,
>>>
>>> I think the fix in
>>> https://github.com/w
How on earth did you test it so fast? It takes 45 minutes just to run
configure on my machine!
Bill.
On 31 March 2014 21:28, Jean-Pierre Flori wrote:
>
>
> On Monday, March 31, 2014 9:20:51 PM UTC+2, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Monday, March 31, 2014 9:15:15 PM UTC+2, Jean-Pierre F
On Monday, March 31, 2014 9:20:51 PM UTC+2, Jean-Pierre Flori wrote:
>
>
>
> On Monday, March 31, 2014 9:15:15 PM UTC+2, Jean-Pierre Flori wrote:
>>
>> Dear all,
>>
>> I think the fix in
>> https://github.com/wbhart/mpir/commit/053476c4567874223180485ff0a4fa808d0ab4d1is
>> actually wrong.
>> Wh
I'll give it a try. It took me nearly a whole day to test on MinGW,
MinGW32, Cygwin and Cygwin64. Now it'll have to be done again, with and
without --enable-cxx. So that's two full days of testing if nothing
breaks.
MinGW, Cygwin and autotools are such piles of turd.
Besides, GMP doesn't do t
On Monday, March 31, 2014 9:15:15 PM UTC+2, Jean-Pierre Flori wrote:
>
> Dear all,
>
> I think the fix in
> https://github.com/wbhart/mpir/commit/053476c4567874223180485ff0a4fa808d0ab4d1is
> actually wrong.
> What you did is basically go back to the previous state of
> configure.in/acwith rega
On 31/03/2014 18:55, Jeff Gilchrist wrote:
> On Fri, Mar 28, 2014 at 4:26 PM, Brian Gladman wrote:
>
>> My repository at:
>> https://github.com/BrianGladman/mpir
>>
>> is fully up to date but I don't think Bill has my latest VS build files.
>
> I pulled your latest master and followed the instru
On 31 March 2014 19:55, Jeff Gilchrist wrote:
> On Fri, Mar 28, 2014 at 4:26 PM, Brian Gladman
> wrote:
>
> > My repository at:
> > https://github.com/BrianGladman/mpir
> >
> > is fully up to date but I don't think Bill has my latest VS build files.
>
> I pulled your latest master and followed t
Dear all,
I think the fix in
https://github.com/wbhart/mpir/commit/053476c4567874223180485ff0a4fa808d0ab4d1
is actually wrong.
What you did is basically go back to the previous state of configure.in/ac
with regards to AC_PROG_CXX.
But note that it should not be run conditionally this way, whenc
On Fri, Mar 28, 2014 at 4:26 PM, Brian Gladman wrote:
> My repository at:
> https://github.com/BrianGladman/mpir
>
> is fully up to date but I don't think Bill has my latest VS build files.
I pulled your latest master and followed the instructions in the
build.vc12\readme.txt file. Good news, i
23 matches
Mail list logo
