Displaying 4 results from an estimated 4 matches for "libobjcopy".
Did you mean:
klibcobjcopy
2016 Dec 14
0
LLD status update and performance chart
...could
speeding up linking (or more generally, incremental builds). It's still not
clear exactly how much speedup can be achieved by doing this, or even where
the speedup will come from.
-- Some people focus a lot on the ability to do O(changes in the input)
work. However, just like in the "libObjcopy" case, this is a much harder
problem that it seems at first and for the same reason. And it's the same
reason that "objcopy" is called "objcopy": really the only way to edit an
object file is to copy it, which intrinsically does O(the output) work. At
the tail end of th...
2016 Dec 14
2
LLD status update and performance chart
...nking (or more generally, incremental builds).
> It's still not clear exactly how much speedup can be achieved by
> doing this, or even where the speedup will come from.
> -- Some people focus a lot on the ability to do O(changes in the
> input) work. However, just like in the "libObjcopy" case, this is a
> much harder problem that it seems at first and for the same reason.
> And it's the same reason that "objcopy" is called "objcopy": really
> the only way to edit an object file is to copy it, which
> intrinsically does O(the output) work. A...
2016 Dec 14
0
LLD status update and performance chart
...nking (or more generally, incremental builds). It's still not
> clear exactly how much speedup can be achieved by doing this, or even where
> the speedup will come from.
> -- Some people focus a lot on the ability to do O(changes in the input)
> work. However, just like in the "libObjcopy" case, this is a much harder
> problem that it seems at first and for the same reason. And it's the same
> reason that "objcopy" is called "objcopy": really the only way to edit an
> object file is to copy it, which intrinsically does O(the output) work. At
>...
2016 Dec 13
3
LLD status update and performance chart
On Tue, Dec 13, 2016 at 12:01 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
> On Dec 13, 2016, at 11:51 AM, Rui Ueyama <ruiu at google.com> wrote:
>
> On Tue, Dec 13, 2016 at 11:37 AM, Mehdi Amini <mehdi.amini at apple.com>
> wrote:
>
>>
>> On Dec 13, 2016, at 11:30 AM, Rui Ueyama <ruiu at google.com> wrote:
>>
>> On Tue, Dec