Re: What would it take to always force indirect inlining?

[Daniel Santos <daniel dot santos at pobox dot com>]

On 07/18/2014 04:55 AM, Martin Jambor wrote:
> Hi,
>
> On Thu, Jul 17, 2014 at 12:26:43PM -0500, Daniel Santos wrote:
> > I've recently discovered that a function marked always_inline but
> > called by pointer won't always be inlined. What would it take to
> > assure that this either always happens or generates an error?
> Generally, that is the case.  Direct non-inlined calls of
> always_inline functions thus indicate that the destination become
> known only after inlining in the optimization pipeline.  Without more
> context, especially without knowing how exactly you call my_quicksort
> function, it is impossible to say why.  If you cannot povide us with
> the source code (I would be interested if you can), you can try
> compiling with -fdump-tree-all -fdump-ipa-all-details and go through
> the generated dump files to find out at what point it becomes known.
> ipa-cp and ipa-inline dumps also contain information about what
> inlining context of your function.
>
> Martin

Hello. I've given it a new home: https://github.com/daniel-santos/cmeta. 
I'm using cmake for the first time and I'm not sure that I like it. For 
now, you have to *manually* specify your CFLAGS. This is what I'm using:

CFLAGS="-std=gnu11 -march=native -g3 -pipe -Wall -Wextra -Wcast-align 
-Wno-unused-parameter -O2 -DNDEBUG"

My -march=native is a Phenom 9850 and I did this on gcc 4.8.3. I have 
4.9.0 installed, but I haven't examined that one just yet, but I will 
shortly. Also please note that this is currently not the worlds 
prettiest code! (sorry, I guess I'm vain)

Daniel