Displaying 2 results from an estimated 2 matches for "n_weak_ref".
Did you mean:
n_weak_def
2018 Feb 16
0
ThinLTO and linkonce_odr + unnamed_addr
...this optimization because of #1 – it seems
> like there should be a way to work around that. Perhaps there's something
> we can change in ld64.
>
As far as I can tell, the "auto hide" property is independent of whether
the symbol is actually hidden (the former is N_WEAK_DEF|N_WEAK_REF in
n_desc, and the latter is N_PEXT in n_type). So perhaps what you can do is
change ld64 to recognize N_WEAK_DEF|N_WEAK_REF together with N_PEXT as
meaning "hidden and mergeable".
Peter
>
> > Steven
> >
> >> On Feb 9, 2018, at 2:00 PM, Steven Wu via llvm-dev <...
2018 Feb 14
2
ThinLTO and linkonce_odr + unnamed_addr
> On Feb 14, 2018, at 09:55, Steven Wu via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> I did a bit more digging for the auto hide problem. Here is my finding that prevent us from doing this by default in GlobalOpts
>
> 1. When a symbol is linkonce_odr hidden unnamed_addr, it emits both '.private_extern' and '.weak_def_can_be_hidden' asm directives on