Like to contribute to g++

[Martin v. Loewis]

> Hi, I would like to help with the effort of adding/testing the "inliner
> for C++" to g++.
> 
> Please let me know how I can be of assistance.

If you want to test code, its best if you use the CVS mainline code,
or the snapshots. To test it, just use it :-) If you find bugs, please
report them using the instructions in

http://gcc.gnu.org/cgi-bin/fom.cgi?file=11

or the section "Reporting Bugs" in the gcc manual.

Of course, it is more valuable if you actually contribute code. There
really is no priority on the order in which things need to be done,
and if you ask different people, you'll get different task lists. Here
is mine, with respect to C++ inlining:

- fix any bugs as they are encountered
- try to perform virtual call analysis to do inlining. If the type
  of an object can be determined statically, the function being called
  can be determined, and might be inlined (if the definition has been
  seen)
- try to perform exception set analysis on a function. Since functions
  became trees, it should be possible to better analyse what exceptions
  can be thrown in what expressions. Accumulate this information (looking
  through inline functions if possible), considering throw specs as they
  are defined. Generate implicit throw specs for inline functions. Using
  that information, produce warnings for exceptions that won't be caught,
  or about dead catch clauses. Also, simplify throw spec code if it can
  be determined that no exception outside the throw spec can ever occur
  in the function.

Regards,
Martin