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: Volatile MEMs in statement expressions and functionsinlinedastrees


>>>>> "Toon" == Toon Moene <toon@moene.indiv.nluug.nl> writes:

> Jason Merrill wrote:

>> No, I think that since the tree inliner uses STMT_EXPRs for inline
>> functions, and functions can return references, we need to support
>> STMT_EXPRs with reference type.  I don't really care what ({ i; }) means.

> Why couldn't the tree-inliner treat inline functions like the Fortran
> frontend treats STATEMENT FUNCTIONs, i.e. by compiling them as (or
> converting them to) inlined nested functions ?

What, treat inline functions as inline functions?  :)

The C and C++ frontends have recently moved to inlining at the tree level,
for various reasons.  I think Fortran still does RTL inlining, right?

Jason


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