__MATH_INLINE - __extern_inline or __extern_always_inline?

[Roland McGrath]

> Two approaches come to mind, the first one would be to define e.g.
> __fortify_function macro, which would contain __extern_always_inline
> and __attribute__((artificial), and then use that __fortify_function
> macro where appropriate in place of __extern_always_inline.  Or, just
> define __attribute_artificial__:

I'd say both.  That is, have __attribute_artificial__ to isolate the
GCC version testing stuff for that.  But also have a single macro that
is the right thing for the _FORTIFY_SOURCE inlines, and give it a name
that is clear about its precise purpose.


Thanks,
Roland