2017-10-06 5:58 GMT+09:00 Doug Anderson :
> Hi,
>
> On Thu, Oct 5, 2017 at 12:26 AM, Masahiro Yamada
> wrote:
>> As far as I tested, I always see only one space after ":=" in v2.
>>
>> I did not consider this deeply,
>> but something is working nicely behind the scene.
>
> Try adding this to the e
Hi,
On Thu, Oct 5, 2017 at 12:26 AM, Masahiro Yamada
wrote:
> As far as I tested, I always see only one space after ":=" in v2.
>
> I did not consider this deeply,
> but something is working nicely behind the scene.
Try adding this to the end of the main Makefile:
+$(info LDFLAGS_BUILD_ID = $(L
Hi Douglas,
2017-10-05 7:38 GMT+09:00 Doug Anderson :
> Hi,
>
> On Tue, Oct 3, 2017 at 9:05 PM, Masahiro Yamada
> wrote:
>> Thanks for the patches. The idea is interesting.
>>
>> I am not a Chrome developer, but cc-option could be improved somehow.
>>
>>
>> I examined two approaches to mitigate
Hi,
On Tue, Oct 3, 2017 at 9:05 PM, Masahiro Yamada
wrote:
> Thanks for the patches. The idea is interesting.
>
> I am not a Chrome developer, but cc-option could be improved somehow.
>
>
> I examined two approaches to mitigate the pain.
>
> [1] Skip cc-option completely when we run non-build ta
Hi Douglas,
2017-09-27 2:55 GMT+09:00 Douglas Anderson :
> While timing a "no-op" build of the kernel (incrementally building the
> kernel even though nothing changed) in the Chrome OS build system I
> found that it was much slower than I expected.
>
> Digging into things a bit, I found that quit
While timing a "no-op" build of the kernel (incrementally building the
kernel even though nothing changed) in the Chrome OS build system I
found that it was much slower than I expected.
Digging into things a bit, I found that quite a bit of the time was
spent invoking the C compiler even though we
6 matches
Mail list logo
