| [cdt-dev] Elf Profiling and potential improvements |
|
Hello world,
I have been profiling CDT's elf parser, and have found some opportunities. Now please understand, I was torture testing it to make sure it works with Trace Compass for some upcoming feature ideas I was going to pitch, I'm just hoping to help more than myself
with this effort.
I was testing an embedded system with a 1 GB executable. Why? in case someone else does that. Elf parsing works well and scaled OK. But the memory requirements are a bit high.
Basically the parser loads every symbol into an array then sorts it. See image below for a "smaller" test with 60k functions.
I have made a quick patch to allow iteration through the elf file instead of reading it all in one block. This is useful when you want to make a map of symbols to trace segments.
I have questions about the API of that file though, it has many public/protected fields that kind of limit its modify-ability, what would be the CDT friendly way to improve it?
My endgame would be to have an iterator on the executable that gives all the symbols, not necessarily in order so an extender can use it with more degrees of freedom.
Thanks!
Matthew
Ericsson
Matthew Khouzam Software Developer Ericsson 8275 Route Transcanadienne H4S 0B6,Saint-Laurent, Quebec Canada Our commitment to Technology for Good and Diversity and Inclusion contributes to positive change. Follow us on: Facebook LinkedIn Twitter Legal entity:ERICSSON AB registration number 556056-6258, registered office in Stockholm This communication is confidential. Our email terms: https://www.ericsson.com/en/legal/privacy/email-disclaimer |