This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
In message <19990218012725.H20100@diwanh.cais.net>you write: > 1. Make and keep the documentation current if at all possible. For > instance, I found no instance of the '-m' switch on the manpage and in the > help, it does not give any mention as to the processors it will support > [I found out about -mpentiumpro through fooling around, which, although > fun, should be unnecesary]. The man pages are not really supported. The GNU project supports documentation in the "info" format. In the distribution you picked up you have a copy of the gcc manual in the info format. You can use emacs to browse that format, or convert it into postscript for printing. All the -m switches for each target should be documented in the manual. > 2. Provide a source trace for what stage of compilation goes where. For > instance, something like this [I have looked but, have been unable to > locate this file]> When compiling a program, comments are stripped in file > blah.c, then the preprocessor function includes(...) is called to > determine and extract the functions from the library, etc. Huh? Can you try to be clearer? I have no idea what you're asking for. > 3. Since most, if not all, egcs developers are on the internet, these > should ideally be stored on high-bandwidth servers. This will reduce the > size of my CVS repository for the compiler by elimating all the texinfo/ > directory and a few more things. "these" refers to what? I don't forsee getting the egcs server co-located directly on bbn's network or anything like that. Such services can cost thousands of dollars per month. Way outside the budget for a project like this. Instead we have to depend on mirror sites to distribute the load of ftp service for the project. jeff