The tree API

Mike Stump mrs@apple.com
Sat Jun 18 05:12:00 GMT 2005


On Thursday, June 16, 2005, at 03:16  AM, ibanez@sunplus.com.tw wrote:
> I'm a new guy in gcc mailing list I've been studying gcc for 2 months.

Why?

> My problem is there are so much symbol/function/API in gcc.

You have two choices ignore what you aren't interested in learning, or 
learn it all.  Your choice.  I'd recommend the former.

> This approach is not effective.

Ok.  Without knowing what you're doing and why you're doing it and how 
you're doing it, we can't give you any more help at being effective.

> If there is a way to learn the gcc internal APIs "systematically"?

Why?

Sounds like you're going about things the wrong way.


General hint, no one is likely to answer your question and give you the 
help you need, as we don't know what answer would help you.  Compare 
the needs of a person that is new to gcc in implementing a language 
front-end for Cobol versus a person that wants to implement a tree 
optimizer for autovectorization.  The answers for each are going to be 
slightly different.  I can't actually tell which of these you are 
doing, or if it is something else.  If you want help, you have to give 
us all the information about what you want to learn, why you want to 
learn it, and what we are going to get back from you for giving you the 
information.  Are we going a port, a new optimizer, a new language 
front end, or just the satisfaction knowing that you got an A on your 
homework?

In general, we can't teach you the code, the code is there for you to 
read and understand and teach yourself.  We can only help with a few of 
the fringes, like, do I need to recompute the cfg after I do X.  Is 
there a function I can call to do this?  Notice that this style of 
question has a few more details about what one is doing, and what 
specifically one needs help on.

Try writing a question that is 4x the size of this (non-)answer.

http://www.catb.org/~esr/faqs/smart-questions.html is a curious 
reference that comes to mind that we just saw go by...



More information about the Gcc mailing list