Hi all,
It takes 15mins+ to link vmlinux.o with 'CONFIG_LTO_CLANG_FULL=y' ('-flto'),
while only takes less than 2mins to link vmlinux.o with
'CONFIG_LTO_CLANG_THIN=y' ('-flto=thin)'.
I compared the code size of ThinLTO and FullLTO(tested with Android ACK
kernel).
vmlinux.o with FullLTO ~= 1.2GB
vmlinux.o with ThinLTO ~=1.1GB
The ThinLTO paper(https://research.google/pubs/pub47584/) says the runtime
performance of FullLTO and ThinLTO are almost the same, based on
applications.
Summarize the aboveļ¼ ThinLTO has smaller code size, matching performance
with FullLTO.
Why doesn't ACK kernel use '-flto=thin'?
--
--
You received this message because you are subscribed to the "Android Building"
mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/android-building/cffbbf01-3a05-418b-ba77-f5f13685f86dn%40googlegroups.com.
