search for: stv_default

...don’t actually honor >> default visibility in the ELF sense, so it’s silly to pretend that LLVM >> visibility is the same as ELF visibility. ELF protected visibility is basically >> the semantics LLVM already assigns to default visibility. > > Except that we still produce STV_DEFAULT. Basically we have a mode > where we handle GVs as if they were protected but produce a > STV_DEFAULT. Yes, I don’t think this is a justifiable position. We either do or do not support interposition of global definitions. > If we are going to drop it, I think the only workable default s...

> 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

...n the main > executable. That is not well supported. I’m sorry, but I didn’t quite get that. The symbol is defined as protected by the dynamic library, but the main executable can’t just use an ordinary external symbol reference to it for some reason? >>> Except that we still produce STV_DEFAULT. Basically we have a mode >>> where we handle GVs as if they were protected but produce a >>> STV_DEFAULT. >> >> Yes, I don’t think this is a justifiable position. We either do or do not support >> interposition of global definitions. > > I don't see...

You are right it creates them but sets the protected flag (STV_PROTECTED) which seems to be the cause of my problem. How can I tell it to set the flag as STV_DEFAULT? Thanks A On 5/28/20, 11:30 PM, "Fangrui Song" <maskray at google.com> wrote: NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 2020-05-28, Moshtaghi, Alireza vi...

...l email. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > > You are right it creates them but sets the protected flag (STV_PROTECTED) which seems to be the cause of my problem. > How can I tell it to set the flag as STV_DEFAULT? > > Thanks > A > > On 5/28/20, 11:30 PM, "Fangrui Song" <maskray at google.com> wrote: > > NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. &...

lld does not seem to create the __start and __end symbols for orphan sections. I would like to keep my linker script as generic as possible so how can I tell lld to create these symbols without having to add them in the linker script? Thanks A -------------- next part -------------- An HTML attachment was scrubbed... URL: