[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inlining doesn't happen on OS X: big performance problem
From: |
Daniel Colascione |
Subject: |
Re: Inlining doesn't happen on OS X: big performance problem |
Date: |
Thu, 19 Sep 2013 13:58:22 -0700 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
On 9/19/13 9:35 AM, Andreas Schwab wrote:
> Daniel Colascione <address@hidden> writes:
>
>> Can we please remove these "!defined __APPLE__" tests and start inlining
>> functions again in OS X?
>
> Why doesn't the compiler inline static functions by itself?
Why should it?
Also, I don't see why we've been going through the tree and replacing
instances of "static inline" with "static": sure, it's possible for the
compiler to inline non-"inline" functions, and even functions marked
"inline" might not get inlined, but "static inline" is a good hint and
makes inlining much more likely. Why should we remove this hint?
signature.asc
Description: OpenPGP digital signature
Re: Inlining doesn't happen on OS X: big performance problem, Andreas Schwab, 2013/09/19
- Re: Inlining doesn't happen on OS X: big performance problem,
Daniel Colascione <=
Re: Inlining doesn't happen on OS X: big performance problem, Paul Eggert, 2013/09/19
Re: Inlining doesn't happen on OS X: big performance problem, Ryan Johnson, 2013/09/19
Re: Inlining doesn't happen on OS X: big performance problem, Paul Eggert, 2013/09/19
Re: Inlining doesn't happen on OS X: big performance problem, Ryan Johnson, 2013/09/19
Re: Inlining doesn't happen on OS X: big performance problem, Jan Djärv, 2013/09/20
Re: Inlining doesn't happen on OS X: big performance problem, Dmitry Antipov, 2013/09/20