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.
Matthias Urlichs: > The current limiting code was, AFAIK, put in because excessive inlining > caused egcs (more specifically, g++) to require a somewhat ugly amount of > swap space. But somebody else can probably answer that question better than > me. No, to my knowledge the patch that limits the size of inlined function is not yet in the egcs sources. The current source still does not limit the size of function marked as inline (I guess that extern inline functions are treated the same way). Note that function not marked as inline can be inlined by the compiler and that there is a size limit for those (but that's not the case discussed in this thread). AFAICT, the patch has not yet incorporated precisely because of concerns about: - having understandable rules (how the limit is expressed and when it is in effect. - breaking the current behaviour of gcc as little as possible. This is clearly an example showing that egcs people are not changing things without being convinced that they do the right thing. The discussion thread subject was "g++ memory bug" for those that are interested. The current list of reasons for which a function would not be inlined has been given by Richard Henderson in a previous message of this thread. Theo. -------------------------------------------------------------------- Theodore Papadopoulo Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01 --------------------------------------------------------------------