You are right about C, but i believe templates in C++ make parsing harder.
DOxygen also parses C/C++.
On 7/29/07, Rafael Espindola <[EMAIL PROTECTED]> wrote:
> > Having spent some time looking at the code for gcc it seems reasonably
> > easy(with some suggestions) to traverse the tree generated a
petruk_gile <[EMAIL PROTECTED]> writes:
> I'm a pure beginner in GCC, and currently working on a project to implement
> instruction scheduling for a new DSP processor. This processor doesn't have
> pipeline interlock, so the compiler HAVE to schedule the instruction without
> relying on hardware h
Hi ALL
I'm a pure beginner in GCC, and currently working on a project to implement
instruction scheduling for a new DSP processor. This processor doesn't have
pipeline interlock, so the compiler HAVE to schedule the instruction without
relying on hardware help anymore
The problem is, I'm a
Hi Mark,
According to gcc/ChangeLog, gcc 4.2.1 was released on 2007-07-19.
Shouldn't gcc/DEV-PHASE in gcc 4.2 branch be marked as prerelease?
H.J.
On Fri, 2007-07-27 at 05:30 -0400, Robert Dewar wrote:
> People asking *language* questions are often told to go
> elsewhere, and that's reasonable. Actually my complaint there
> would be that too often, people on this list answer such off
> topic questions (which is fine), and copy the answers to
On 27 July 2007 18:24, Ian Lance Taylor wrote:
> "Pranav Bhandarkar" writes:
>
>> I am working on a private port and am seeing the following problem.
>> For a function returning a double the value is stored by the function
>> in memory. cse removes one of the two loads (to retrieve this returned
"吴曦" <[EMAIL PROTECTED]> writes:
> Sorry, I didn't find that pass in gcc 4.1.1. This pass is added in the
> newest gcc?
I see from your later message that you found it.
> > allocation. It means that the prologue and epilogue instructions are
> ~~
> As you have indicated, this pass happe
> Having spent some time looking at the code for gcc it seems reasonably
> easy(with some suggestions) to traverse the tree generated and
> write the relevant information to a file. Any suggestions or pointers to
> related work would be much appreciated.
For C and C++, it might be easier to us
That isn't what I see here. The output binary was definately for a v8plus
processor. That would be a UltraSparc 1 at the least.
There is no real V8+ architecture, V8+ is an augmented 32-bit ABI for the V9
architecture, the native ABI of the V9 architecture being the 64-bit ABI.
The mapping bet
