On 22/03/2008, 梁�� <[EMAIL PROTECTED]> wrote: > > Any advice to be invovled in development of gcc ? > Thank you very much. > Sorry for disturbing.
http://gcc.gnu.org/wiki/GettingStarted My advice would be: * Narrowly focus on what you are truly interested in: front-end, middle-end, back-end. Don't try to understand everything at once. For example, you don't need to understand the backend or RTL to modify the front ends. * Be prepared to use GDB. Many times the only way to figure out how some code works is to step through some testcase. There are too many code paths in GCC to document all of them. The resulting documentation would be just a pseudo-code version of the real code. More abstraction would be welcome, though. * Ask questions here (or in the irc channel) but be precise when asking. "How does the backend works?" is a bad question: it can't be answered in few words and there is substantial documentation available. Yes/no questions are typically the best. * Choose a small project or even just a bug to fix. Feedback on patches is typically more precise than the answer of general questions. You will learn more by trying and failing a few times than by printing the source code and reading it. * And finally, be patient and persistent. Cheers, Manuel. P.S.: Of course, anything that you think that can be improved in the documentation (web pages, wiki, etc.), comments in the code or the code itself, please change it! The wiki is particularly easy to change.
