Basile Starynkevitch wrote, On Tuesday 15 January 2013 11:34 AM:
On Tue, Jan 15, 2013 at 11:16:54AM +0530, 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.or
On Tue, Jan 15, 2013 at 11:16:54AM +0530, 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++. Howeve
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 very first line of the description
confused me. It says:
GCC has
On 01/14/2013 04:50 PM, David Daney wrote:
On 01/14/2013 04:32 PM, reed kotler wrote:
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
The mips16ness of a function must be known by the caller so that the
appropriate version of the JAL/JALX instruction can b
On 01/14/2013 04:32 PM, reed kotler wrote:
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
The mips16ness of a function must be known by the caller so that the
appropriate version of the JAL/JALX instruction can be emitted
i..e you should be able to sa
I'm not understanding why mips16 and nomips16 are not simple inheritable
attributes.
i..e you should be able to say:
void foo();
void __attribute((nomips16)) foo();
or
void goo();
void __attribute((mips16)) goo();
There does not seem to be any other cases in gcc where this would not be
all
> Then it is expected that dwarf debug is much bigger than stabs debug,
> since the latter does not include any of the value tracking capabilities
> of dwarf. Without that it is almost impossible for a debugger to
> display the true value of local variables.
Indeed. And it would be interesting t
David Taylor writes:
> Optimized, -O2.
Then it is expected that dwarf debug is much bigger than stabs debug,
since the latter does not include any of the value tracking capabilities
of dwarf. Without that it is almost impossible for a debugger to
display the true value of local variables.
Andr
On Mon, Jan 14, 2013 at 2:00 AM, Thomas Baier wrote:
> Dear list,
>
> I've just subscribed to the list and I hope this is the right place for
> the following question.
>
> The operating system I'd like to use gcc for (OS-9, for the curious)
> requires an ABI, where global variables are only access
On Mon, 14 Jan 2013 17:12:25 +0100, Doug Evans wrote:
> Not that I think it's a priori worth the effort to dig deeper, but for
> another datapoint, Redhat added an lza-compressed mini-dwarf-debug
> section. I'm not sure what it supports (if anything beyond making
> backtraces better).
It can cont
>> Next, I compiled a 5000-line C++ source file at both -O0 and -O2.
>
> I have to assume that David is working with C code, as stabs debugging
> for C++ is nearly unusable.
I assumed that too, but I figured C++ would be worse than C as far as
DWARF vs. stabs size. I'd still be interested to figur
Andreas Schwab wrote:
> David Taylor writes:
>
> > {As to what d90f.elf is -- that's unimportant; but, it's the kernel for
> > one of the boards in one of our hardware products.]
>
> Is it an optimized or an unoptimized build?
Optimized, -O2. According to find piped to wc, there's 2587 C fil
On Mon, 2013-01-14 at 08:00 +0100, Thomas Baier wrote:
> The operating system I'd like to use gcc for (OS-9, for the curious)
> requires an ABI, where global variables are only accessed through
> register indirect addressing. On the powerpc platform, r2 is used for
> indirect addressing. There is a
On Mon, Jan 14, 2013 at 10:03 AM, Eric Botcazou wrote:
>> The Mac OS 9 ABI is very similar to the AIX ABI. So you should be
>> able to start with the AIX ABI and go from there.
>
> Are you sure that you're talking about the same OS-9 as Thomas here?
Oh OS-9. Anyways it does sound more like the
> The Mac OS 9 ABI is very similar to the AIX ABI. So you should be
> able to start with the AIX ABI and go from there.
Are you sure that you're talking about the same OS-9 as Thomas here?
--
Eric Botcazou
On Sun, Jan 13, 2013 at 11:00 PM, Thomas Baier wrote:
> Dear list,
>
> I've just subscribed to the list and I hope this is the right place for
> the following question.
>
> The operating system I'd like to use gcc for (OS-9, for the curious)
> requires an ABI, where global variables are only acces
On Fri, Jan 11, 2013 at 6:55 PM, Cary Coutant wrote:
>>> If I use objcopy --compress-debug-sections to compress the DWARF debug
>>> info (but don't use it on the STABS debug info), then the file size
>>> ratio is 3.4.
>>>
>>> While 3.4 is certainly better than 11.5, unless I can come up with a
>>>
On 01/01/2013 10:53 AM, Shakthi Kannan wrote:
Greetings!
I would like to know if there are any TODO tasks that I can work on to
get started with Graphite/GCC. I came across Tobias Grosser's post
regarding Graphite development at:
http://gcc.gnu.org/wiki/Graphite-4.8
If you have any suggesti
On Fri, Jan 11, 2013 at 7:17 PM, Ian Lance Taylor wrote:
> On Fri, Jan 11, 2013 at 5:55 PM, Cary Coutant wrote:
>>
>> Next, I compiled a 5000-line C++ source file at both -O0 and -O2.
>
> I have to assume that David is working with C code, as stabs debugging
> for C++ is nearly unusable.
That wa
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
test if x is NaN.
--
Marc Glisse
On 01/14/2013 08:34 AM, Mischa Baars wrote:
> When running the example attached, you can see the compiler fails to
> recognize not-a-number's properly.
>
> Anyone who would like to have a look?
Comparing NaN with anything always returns false. Even when comparing
with NaN.
You want:
i
On Mon, Jan 14, 2013 at 9:34 AM, Mischa Baars wrote:
> Hi,
>
> When running the example attached, you can see the compiler fails to
> recognize not-a-number's properly.
>
> Anyone who would like to have a look?
THat's how FP works. Use isnan().
Richard.
> Regards,
> Mischa.
Dear list,
I've just subscribed to the list and I hope this is the right place for
the following question.
The operating system I'd like to use gcc for (OS-9, for the curious)
requires an ABI, where global variables are only accessed through
register indirect addressing. On the powerpc platform,
Hi,
When running the example attached, you can see the compiler fails to
recognize not-a-number's properly.
Anyone who would like to have a look?
Regards,
Mischa.
#include
#include
int main()
{
double x = NAN;
if (x == NAN)
{
printf("found a not-a-number\n");
}
return;
}
On Fri, Jan 11, 2013 at 5:41 PM, Joseph S. Myers
wrote:
> On Fri, 11 Jan 2013, Michael Zolotukhin wrote:
>
>> > Personally I'd think a natural starting point on the compiler side would
>> > be to write a reasonably thorough and systematic testsuite for such
>> > issues. That would cover all opera
25 matches
Mail list logo
