Displaying 3 results from an estimated 3 matches for "notifyfileaddedcontent".
2013 Sep 21
1
[LLVMdev] LLD input graph handling proposal
...nks. I assume part of this change is to unify those two methods by just have one loop that uses nextFile().
Given that nextFile() is basically an iteration mechanism, perhaps we can make it conform to C++11 iterators. The one issue is the feedback of whether the file was used or not. A separate notifyFileAddedContent() method (instead of a parameter to nextFile()) could fix that. And if Resolver::doFile() called linkingContext.notifyFileAddedContent() for every file used (even object files), then the Resolver algorithm would look like:
for (File *file : linkingContext) {
if (file.kind() == object...
2013 Sep 21
0
[LLVMdev] LLD input graph handling proposal
Hi Nick,
Read this along with this example extract:
ld -flavor gnu main.o thread.o --start-group libc.a libpthread.a
--end-group function.o
main.o has atoms
------------------------
main (defined)
printf(undefined)
fn(undefined)
thread.o has atoms
-----------------------------
pthread_create (undefined)
libc.a(printf.o) has atoms
------------------------------------
printf(defined)
2013 Sep 21
2
[LLVMdev] LLD input graph handling proposal
Hi,
Attached is the pdf of the operation to make things easier to read.
Thanks
Shankar Easwaran
On 9/20/2013 7:04 PM, Shankar Easwaran wrote:
> My email client spoilt the whole email, will create a pdf and send it.
>
> On 9/20/2013 7:00 PM, Shankar Easwaran wrote:
>> Hi Nick,
>>
>> On 9/20/2013 5:59 PM, Nick Kledzik wrote:
>>> On Sep 20, 2013, at 3:42 PM,