Displaying 5 results from an estimated 5 matches for "weakany".
Did you mean:
wakano
2016 Nov 29
2
RFC: Add an "interposible" linkage type (and implement -fsemantic-interposition)
...ul because we want
> > the old weak to decode as weak+interposable and the old weak_odr to
> > decode as weak.
>
> > Some more prior discussion: https://reviews.llvm.org/D19995#423481
>
> +1
So we're all on the same page, our current encodings are:
External: 0
WeakAny: 16
Appending: 2
Internal: 3
LinkOnceAny: 18
ExternalWeak: 7
Common: 8
Private: 9
WeakODR: 17
LinkOnceODR: 19
AvailableExternally: 12
And the new encodings would be:
External: 0
External + Interposible: 20
Weak + Interposible: 16
Appending: 2 [interposible N/A]
Internal: 3 [never i...
2015 Jul 14
3
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
...attached the doc in pdf form, since
the formatting (especially for the table at the end) may not come through
in the copied text below well.
Thanks!
Teresa
ThinLTO Symbol Linkage and Renaming
1 Introduction
2 Non-Discardable Values
2.2 Linkage Effects
2.2.2 ExternalLinkage
2.2.1 WeakAnyLinkage
2.2.2 WeakODRLinkage
2.2.3 AppendingLinkage
2.2.4 CommonLinkage
3 Linkonce Values
3.1 Linkage Effects
3.2 Importing Strategy
4 Static Values
4.1 Static Variables
4.2 Static Functions
4.3 Static Promotion
4.3.1 Linkage Effects
4.3.2 Renaming
5 Linkage...
2015 Jul 21
1
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
...ext below well.
> >
> > Thanks!
> > Teresa
> >
> >
> > ThinLTO Symbol Linkage and Renaming
> >
> >
> > 1 Introduction
> > 2 Non-Discardable Values
> > 2.2 Linkage Effects
> > 2.2.2 ExternalLinkage
> > 2.2.1 WeakAnyLinkage
> > 2.2.2 WeakODRLinkage
> > 2.2.3 AppendingLinkage
> > 2.2.4 CommonLinkage
> > 3 Linkonce Values
> > 3.1 Linkage Effects
> > 3.2 Importing Strategy
> > 4 Static Values
> > 4.1 Static Variables
> > 4.2 Static F...
2015 Jul 21
2
[LLVMdev] RFC: ThinLTO Symbol Linkage and Renaming
...t; +----------------------------------------------------------------------------------+
> > | LinkOnceODR (def) | LinkOnceODR | N/A (force
> import def) |
> >
> +----------------------------------------------------------------------------------+
> > | WeakAny (def) | N/A (never import) |
> ExternalWeak |
> >
> +----------------------------------------------------------------------------------+
> > | WeakODR (def) | WeakODR |
> ExternalWeak |
> >
> +-----...
2016 Nov 29
4
RFC: Add an "interposible" linkage type (and implement -fsemantic-interposition)
I think that all makes sense. You're just adding the missing non-ODR
conterpart of 'external' linkage. I could imagine having "external /
external_odr" linkage for example.
That said, do you think we should take the opportunity to split out a bit
for interposability so that we can kill off the *_odr linkage variants?
Today's non-ODR weak functions would look more like