Hi, On Wed, 6 May 2015, Rich Felker wrote:
> I don't see how this case is improved unless GCC is failing to consider > strong definitions in the same TU as locally-binding. Interposition of non-static non-inline non-weak symbols is supported independend of if they are defined in the same TU or not (if you're producing a shared lib, that is). I.e. no, they are not considered locally-binding (for instance, they aren't automatically inlined). > If this is the case, is there a reason for that behavior? Because IMHO interposition is orthogonal to TU placement, and hence shouldn't be influenced by it. There's visibility, inline hints or static-ness to achieve different effects. (perhaps the real reason is: because it always worked like that :) ) > IMO it's wrong. Why? I think it's right. Ciao, Michael.
