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]

Re: [tree-ssa] Non-transitive inlining plans


Hi,

this is really nice.  Does this mean we now correctly track every
call expression in the callgraph?  So this would mean we can do
inlining decisions per call and not just per function (like doing
more agressive inlining inside loops and frequently executed places?).
This would also make some more explicit control over inlining possible,
as the much anticipated __attribute__((leafify)) and/or common #pragmas
like
#pragma inline
to inline the following call, or
#pragma inline complete
as the equivalent to __attribute__((leafify)) at the call site. All these
sort of pragmas can be found in HPC compilers.

Thanks for your continued work on improving inlining!

I'll try to bring forward my __attribute__((leafify)) work to tree-ssa
once this new inlining infrastructure has settled a bit.

Richard.

--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]