This may be useful:
http://gcc.gnu.org/wiki/DebuggingGCC
And in general the info here:
http://gcc.gnu.org/wiki/GettingStarted
It is a wiki, so contributions and fixes are very welcome.
Thanks,
Manuel.
On 18 June 2010 10:55, Radu Hobincu wrote:
>> "Radu Hobincu" writes:
>>
>>> The compiler
> "Radu Hobincu" writes:
>
>> The compiler crashes with "Segmentation fault".
>
>> 2. When I try "char c = 'c';", the compiler fails an assert:
>
> It's time to break out the debugger and look at the source code and
> figure out what the compiler is doing. Neither of these problems ring
> any sor
"Radu Hobincu" writes:
> The compiler crashes with "Segmentation fault".
> 2. When I try "char c = 'c';", the compiler fails an assert:
It's time to break out the debugger and look at the source code and
figure out what the compiler is doing. Neither of these problems ring
any sort of bell for
Hello again,
I managed to get the thing working and I have two last issues to solve.
1. My machine does not have any kind of floating point instructions. When
I write in the C source code
float f = 0.5f;
The compiler crashes with "Segmentation fault". Running a gdb on it, the
output becomes
Pr
"Radu Hobincu" writes:
> Thanks for the reply. I scrolled a lot through the i386 md and c files. I
> notice that the i386 architecture has dedicated
> instructions for comparing values and ALU instructions only specify
> (clobber (reg:CC FLAGS_REG)). What I do not understand is how they specify
>
Thanks for the reply. I scrolled a lot through the i386 md and c files. I
notice that the i386 architecture has dedicated
instructions for comparing values and ALU instructions only specify
(clobber (reg:CC FLAGS_REG)). What I do not understand is how they specify
the way ALU instructions affect th
"Radu Hobincu" writes:
> I have written here a few weeks ago regarding some tutorials on GCC
> porting and got some very interesting replies. However, I seem to have
> gotten stuck with a couple of issues in spite of my massive Googling, and
> I was wondering if anyone could spare a couple of min
Hello again,
I have written here a few weeks ago regarding some tutorials on GCC
porting and got some very interesting replies. However, I seem to have
gotten stuck with a couple of issues in spite of my massive Googling, and
I was wondering if anyone could spare a couple of minutes for some
clari
palpar writes:
> 1. How can I tell from the RTL declaration of a function if it is
> declared INLINE of not?
You have to look at the tree decl, at DECL_DECLARED_INLINE_P.
> 2. Where is the code responsible for allocating those variables on the
> stack which don't fit in registers (needed to fix
Hi all,
I'd have two questions needed for work on porting gcc-3.2.3.
1. How can I tell from the RTL declaration of a function if it is
declared INLINE of not?
2. Where is the code responsible for allocating those variables on the
stack which don't fit in registers (needed to fix debug info
generat
10 matches
Mail list logo
