On Tue, Jan 15, 2013 at 11:36:53AM +0530, Uday P. Khedker wrote:
>
>
> Basile Starynkevitch wrote, On Tuesday 15 January 2013 11:34 AM:
> >My belief is that it is no more possible to configure a recent GCC straight
> >(non-cross) compiler without --enable-language=c++
> >(that is, if you ask only
On Tue, Jan 15, 2013 at 6:46 AM, Uday P. Khedker wrote:
> I was trying to understand the exact meaning of a loose statement
> floating around ("gcc has moved to C++ from version 4.7 onwards).
>
> I reckon from http://gcc.gnu.org/wiki/gcc-in-cxx that now gcc is
> compiled using C++. However, the ve
Richard Biener wrote:
On Tue, Jan 15, 2013 at 6:46 AM, Uday P. Khedker wrote:
GCC has been building stages 2 and 3 in C++ mode for a while.
The C++ compiler is created anyway since 4.7 and is used to build
stage2+. Starting with GCC 4.8 stage1 requires a C++ host compiler.
In GCC 4.7 you c
Hello,
In this stabs vs. dwarf discussion, so far it's more been about
assumptions than numbers. So let's throw in some numbers!
The following debug sizes are for CSiBE-v2.1.1 on mipsisa64-elf, with
the LRA branch at r195108. All CSiBE test cases are packages written
in C.
Debug size is computed
On 01/14/2013 03:50 PM, Marc Glisse wrote:
On Mon, 14 Jan 2013, Mischa Baars wrote:
When running the example attached, you can see the compiler fails to
recognize not-a-number's properly.
Bug reports go to bugzilla.
NaN doesn't compare equal to anything. x==x is actually the usual way
to te
This is what I was trying to point out:
When disregarding the 'isnan()', the function is returning a '2' when
one or both the arguments is a NaN. Do you suppose this is correct?
If you ask me, it should exit on the first compare and thus return a
not-a-number.
Regards,
Mischa.
2010100706
> When disregarding the 'isnan()', the function is returning a '2' when
> one or both the arguments is a NaN. Do you suppose this is correct?
>
> If you ask me, it should exit on the first compare and thus return a
> not-a-number.
You cannot "exit" a comparison in C, one of the branches is always
On Tue, 15 Jan 2013 11:09:46 +0100, Steven Bosscher wrote:
> Unless someone can shoot holes in this test approach,
While the sum of *.o files sizes may make sense in some cases I would find
more useful to measure it only for the final executables and after they have
been processed by dwz.
Besides
On 01/11/2013 07:20 PM, Michael Eager wrote:
I still think it's a bit odd. Other targets use the comparison
operator (e.g., lt, ge, etc.). Microblaze should as well.
Microblaze can't use the raw comparison operator because of how
the results of the cmp{,u} instructions are defined, especially
On Tue, Jan 15, 2013 at 6:53 PM, Jan Kratochvil wrote:
> On Tue, 15 Jan 2013 11:09:46 +0100, Steven Bosscher wrote:
>> Unless someone can shoot holes in this test approach,
>
> While the sum of *.o files sizes may make sense in some cases I would find
> more useful to measure it only for the final
On 01/15/2013 05:24 PM, Eric Botcazou wrote:
When disregarding the 'isnan()', the function is returning a '2' when
one or both the arguments is a NaN. Do you suppose this is correct?
If you ask me, it should exit on the first compare and thus return a
not-a-number.
You cannot "exit" a compariso
On 01/15/2013 05:24 PM, Eric Botcazou wrote:
When disregarding the 'isnan()', the function is returning a '2' when
one or both the arguments is a NaN. Do you suppose this is correct?
If you ask me, it should exit on the first compare and thus return a
not-a-number.
You cannot "exit" a compariso
On Fri, Jan 11, 2013 at 2:29 AM, Louis-Philippe Brais
wrote:
> Hi all,
>
> The latest errata for Texas Instruments' Cortex-M3 family, updated
> last October [1], contains a disturbing new problem triggered by
> non-word-aligned writes to SRAM. This is the kind of errata that is
> effectively addre
> Well, I have an Intel manual here that states that any operation on a
> QNaN should return a QNaN, which means that also the compare should
> return a QNaN when one or both of the arguments is a QNaN.
No, that isn't how comparisons work. The correct result is 2 according to the
comparison rule
14 matches
Mail list logo
