On 7 Mai, 03:20, Gonzalo Tornaria wrote:
> On Thu, May 6, 2010 at 7:58 PM, Dr. David Kirkby
>
> wrote:
> > ...
> > The recent case of gcc accepting the macro INFINITY even when code was not
> > compiled in C99 mode was just one example. INFINITY was not defined until
> > the C99 standard.
> > .
Gonzalo Tornaria wrote:
On Thu, May 6, 2010 at 7:58 PM, Dr. David Kirkby
wrote:
...
The recent case of gcc accepting the macro INFINITY even when code was not
compiled in C99 mode was just one example. INFINITY was not defined until the
C99 standard.
...
I must admit, I find it somewhat annoy
On Thu, May 6, 2010 at 7:58 PM, Dr. David Kirkby
wrote:
> ...
> The recent case of gcc accepting the macro INFINITY even when code was not
> compiled in C99 mode was just one example. INFINITY was not defined until the
> C99 standard.
> ...
> I must admit, I find it somewhat annoying that gcc is
On Thu, May 6, 2010 at 3:58 PM, Dr. David Kirkby
wrote:
> Bill Hart wrote:
>>
>> Hi William,
>>
>> What are the major differences in GCC 4.5.0 which seem to be affecting
>> Sage? Is there something new that we should be aware of when writing
>> code for this compiler?
>>
>> Bill.
>
> I don't know
Bill Hart wrote:
Hi William,
What are the major differences in GCC 4.5.0 which seem to be affecting
Sage? Is there something new that we should be aware of when writing
code for this compiler?
Bill.
I don't know if it is such a good idea worrying about gcc 4.5 just now. Note
that the gcc 4.4
On 27 Apr., 18:23, Bill Hart wrote:
> What are the major differences in GCC 4.5.0 which seem to be affecting
> Sage? Is there something new that we should be aware of when writing
> code for this compiler?
>From GCC NEWS:
* On x86 targets, code containing floating-point calculations may
run
On Tue, Apr 27, 2010 at 11:37 AM, Bill Hart wrote:
> OK, thanks. That means I need to make some changes to flint1. I will
> try to do this before Sage 5 comes out. flint2 will be immune and
> won't be out till at least July I have decided.
See http://trac.sagemath.org/sage_trac/ticket/8771
Willi
OK, thanks. That means I need to make some changes to flint1. I will
try to do this before Sage 5 comes out. flint2 will be immune and
won't be out till at least July I have decided.
Bill.
On Apr 27, 6:58 pm, William Stein wrote:
> On Tue, Apr 27, 2010 at 9:23 AM, Bill Hart
> wrote:
> > Hi Wil
On Tue, Apr 27, 2010 at 9:23 AM, Bill Hart wrote:
> Hi William,
>
> What are the major differences in GCC 4.5.0 which seem to be affecting
> Sage?
(1) New bug(s) in GCC-4.5.0, especially optimization related issues :-)
(2) Tighter adherence to C++ standards.
> Is there something new that we sho
Hi William,
What are the major differences in GCC 4.5.0 which seem to be affecting
Sage? Is there something new that we should be aware of when writing
code for this compiler?
Bill.
On Apr 26, 9:15 pm, William Stein wrote:
> Hi,
>
> Main point of this email: if anybody else is trying to port Sa
On Tue, Apr 27, 2010 at 08:46:59AM +0200, Clement Pernet wrote:
> Hi,
>
> I could not find a gcc-4.5 install on eno, to replicate the bug.
> On which machine did you run it? (before I start compile it!)
> Could you also attach the linbox config.log to ticket #8769 ?
Hi Clement,
The issue in #876
Hi,
I could not find a gcc-4.5 install on eno, to replicate the bug.
On which machine did you run it? (before I start compile it!)
Could you also attach the linbox config.log to ticket #8769 ?
Thanks.
Clément
William Stein a écrit :
Hi,
Main point of this email: if anybody else is trying to
On Mon, Apr 26, 2010 at 5:14 PM, kcrisman wrote:
>
>
> On Apr 26, 4:15 pm, William Stein wrote:
>> Hi,
>>
>> Main point of this email: if anybody else is trying to port Sage work
>> with GCC-4.5.0, we won't duplicate effort.)
>>
>> I'm working on trying to port Sage-4.4 to GCC-4.5.0. There are m
On Apr 26, 4:15 pm, William Stein wrote:
> Hi,
>
> Main point of this email: if anybody else is trying to port Sage work
> with GCC-4.5.0, we won't duplicate effort.)
>
> I'm working on trying to port Sage-4.4 to GCC-4.5.0. There are many
> issues on various OS's.
>
> * pynac (solved) --http:
14 matches
Mail list logo
