Re: RFC: weakref GCC attribute and .weakref assembly directive

2005-10-18 Thread Aaron W. LaFramboise
Alexandre Oliva wrote: On Oct 13, 2005, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote: > The difference is that ".weak sym1 = sym2" resolves to sym1 (if available) else sym2; but ".weakref sym1, sym2" resolves to sym2 (if available) else zero. Also sym1 does not become an external, only a local

Re: RFC: weakref GCC attribute and .weakref assembly directive

2005-10-18 Thread Alexandre Oliva
On Oct 13, 2005, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote: > On Thu, Oct 13, 2005 at 08:33:01AM -0500, Aaron W. LaFramboise wrote: >> Could you compare your novel weak references to PECOFF's notion of "weak >> externals"? >> >> .weak sym1 = sym2 # Analogous to: .weakref sym1, sym2 > The dif

Re: RFC: weakref GCC attribute and .weakref assembly directive

2005-10-13 Thread Daniel Jacobowitz
On Thu, Oct 13, 2005 at 08:33:01AM -0500, Aaron W. LaFramboise wrote: > Could you compare your novel weak references to PECOFF's notion of "weak > externals"? > > .weak sym1 = sym2 # Analogous to: .weakref sym1, sym2 > > "If a definition of sym1 is linked, then an external reference to the > s

Re: RFC: weakref GCC attribute and .weakref assembly directive

2005-10-13 Thread Aaron W. LaFramboise
Hello, Alexandre Oliva wrote: What we need, in contrast, is some means to define an alias that doesn't, by itself, cause an external definition of the symbol to be brought in. If the symbol is referenced directly elsewhere, however, then it must be defined. This is similar to the notion of we