search for: stv_proteced

...-fsemantic-interposition to be the default. That is, on > ELF systems we would match GCC: with -fPIC we don't inline non-odr > symbols that end up as STV_DEFAULT. > > In summary, I think it is important that > > * a __attribute__((visibility("protected"))) maps to STV_PROTECED > * by default a decl with no attributes maps to STV_DEFAULT It’s not really my place to decide whether or not -fsemantic-interposition should be the default, so I’ll leave this up to others to debate. My instinct is that interposition is not actually important to very many people, and that th...

> On Mar 11, 2016, at 11:26 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >> Now, there are a number of things about linkage that are kindof orthogonal, >> and it would be nice to model them more orthogonally. That would be a major >> change in representation, though. Absent the will to do that, I propose >> that we: >> - remove/deprecate

...that we allow interposition, but calls within the linkage unit might ignore it, depending on how much our optimizer sees. That’s not a coherent position. >>> In summary, I think it is important that >>> >>> * a __attribute__((visibility("protected"))) maps to STV_PROTECED >>> * by default a decl with no attributes maps to STV_DEFAULT >> >> It’s not really my place to decide whether or not -fsemantic-interposition should be >> the default, so I’ll leave this up to others to debate. >> >> My instinct is that interposition is no...