GNU Arm Embedded Toolchain

Personal question about lto option

Asked by XuXiaodong

Hi all,

    I want to use lto option in my project, in build map:

 .text.coap_address_equals.lto_priv.2610
                0x00000000080515b4 0x30 /tmp/ccTSm5tg.ltrans3.ltrans.o
                0x00000000080515b4 coap_address_equals.lto_priv.2610

.text.coap_find_observer
                0x00000000080515e4 0x50 /tmp/ccTSm5tg.ltrans3.ltrans.o

 .text.coap_delete_all.part.5
                0x00000000080517ae 0x16 /tmp/ccTSm5tg.ltrans3.ltrans.o
 .text.coap_free_context.part.7
                0x00000000080517c4 0xa2 /tmp/ccTSm5tg.ltrans3.ltrans.o
                0x00000000080517c4 coap_free_context.part.7

Does the symbol cannot show it's path like ../../../../../out/proj/obj/middleware/third_party/lwm2m/core/observe.o?

In symbol coap_address_equals.lto_priv.2610, what's meaning about .lto_priv.2610, and the number have special meaning?
Also, symbol .text.coap_delete_all.part.5 what is meaning about part.5?

Best Regards,
HaleyXu

Question information

Language:
English Edit question
Status:
Solved
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Solved by:
john
Solved:
Last query:
Last reply:
Revision history for this message
Best john (jkovach) said : 		#1

I don't think it's worth trying to make sense out of these parts of the make file. LTO is there to provide aggressive optimization, typically code from different source files will be mixed together into something incomprehensible. Just leave it alone.

Revision history for this message
XuXiaodong (haleyxu) said : 		#2

Thanks john, that solved my question.