austern at apple.com
Fri Mar 7 21:19:03 UTC 2003
On Friday, March 7, 2003, at 01:12 PM, Richard Guenther wrote:
> GCC is not very smart at inlining, and with not tuning -finline-limit
> get (due to top-down inlining) trivial methods like FillLocStorageImpl
> stuff and even ~Loc<1> not inlined which hurts performance a lot. GCC
> of version 3.2 (I think) has the ability to mark functions as "always
> inline". This unfortunately cannot be turned on by sth like #define
> __attibute__((always_inline)), but needs to be manually done.
> would be all Domain related stuff and possibly Mesh and Engine stuff as
> well (yes - I get non-inlined Engine::read()s, too...).
> Seems like a mess to me (note: intel icpc isnt any better here). I hope
> we can sneak something like the -fobey-inline patch from Matt Austern
> (see http://gcc.gnu.org/ml/gcc/2003-02/msg01666.html for discussion,
> havent found the actual patch, Matt?) into gcc 3.3/3.4... Mark?
The reason you haven't found the patch is that I didn't submit it.
Stuart Hastings (also from Apple) submitted it. So far it's neither
been approved nor rejected.
More information about the pooma-dev