This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, I am sending this document as an experiment. The CFG branch work has been done from major part as student software project and thus we were required to write documentation. The documentation contain description of each optimization pass we've implemented, programmer's documentation for CFG datasturctures and short sumarry of reached goals (effectivity of the optimizations based on Andrea's SPEC2000 benchmarks). I don't think it is practical do keep whole documentation as it is, as it will not match any of official GCC version. I plan to convert the CFG part from latex to texinfo and try to put it as part of GCC internals manual, but I am not sure what to do with the rest. I don't think it is practical to put it into the documentation as it is dificult to maitain up-to-date. So I've split out the chapter about the tracer pass I sent into the mainline into separate article. Perhaps it can be usefull to put them separately somewhere on the web pages, or link from news if the new pass will get approved. What do you think? Honza
Attachment:
tracera.ps.gz
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |