[LLVMdev] LLD input graph handling proposal
kledzik at apple.com
Fri Sep 20 15:29:24 PDT 2013
I like this in general, but have a few questions.
On Sep 20, 2013, at 2:30 PM, Rui Ueyama <ruiu at google.com> wrote:
> 2. We would instead add a new method nextFile() to LinkingContext, which returns a new file from which Resolver should try to resolve undefined symbols. Resolver wouldn't handle the input graph at all. Instead, Resolver calls nextFile() repeatedly to link until nextFile() returns a null value.
> 3. Resolver will notify Linking Context when (A) all undefined symbols are resolved (success), or (B) it detects it's in an infinite loop in which it cannot resolve any symbols anymore (failure). Linking Context will do whatever it thinks appropriate for the event notification.
How does the Resolver detect an infinite loop? As in the example below, it is supposed to keep getting a,b,c,a,b,c… At some point, no more undefines are being fulfilled by a,b,c,a,b,c…, but how does the resolver know that the files are repeating, to know to tell the InputGraph to move on?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev