search for: moduley

...ed from an example in my response just now to pcc): If a module contains the following, and both @x and @y are non-prevailing in that module: @x = weak global ... @y = weak alias @x and the prevailing def for @x is in moduleX with a different value than the prevailing def for @y which comes from moduleY. Just because they are aliased in this module doesn't mean they must be aliased elsewhere, right? For this case (weak non-prevailing alias to a weak non-prevailing def) I think it should eventually become: @x = external global @y = external global Trying to understand how this fits with your...

...the following, and both @x and @y are non-prevailing > > in that module: > > > > @x = weak global ... > > @y = weak alias @x > > > > and the prevailing def for @x is in moduleX with a different value than > the > > prevailing def for @y which comes from moduleY. Just because they are > > aliased in this module doesn't mean they must be aliased elsewhere, > > right? > > Correct. > > > For this case (weak non-prevailing alias to a weak non-prevailing def) I > > think it should eventually become: > > > > @x =...

Hi Mehdi, Peter and David (and anyone else who sees this), I've been playing with some examples to handle the weak symbol cases we discussed in IRC earlier this week in the context of D28523. I was going to implement the support for turning aliases into copies in order to enable performing thinLTOResolveWeakForLinkerGUID on both aliases and aliasees, as a first step to being able to drop

Thanks, David and Peter. Some responses to Peter's email below. Teresa On Fri, Jan 13, 2017 at 3:21 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Hi Teresa, > > I think that to answer your question correctly it is helpful to consider > what is going on at the object file level. For your test1.c we conceptually > have a .text section containing the body of f, and