* Qing Zhao: > Our internal customer is asking for this feature. > > They used icc currently, with icc, then can get inline list, prof_used > list, etc. from the binary. > > The old studio compiler also provided such feature, there was compiler > commentary section in the binary to record many of the important > compiler transformations along with the line number information. > > If there is any performance issue with the application, such > information will be very useful. Especially for large applications.
We have similar needs and use annobin for that. Its optimization coverage is not great, though. I think for guiding future GCC development, it would be really interesting to know how many (e.g.) memcpy calls are there because the source code was not built with source fortification, or because it was and the compiler deemed the call to be statically safe and not needing bounds checking, or it didn't have any bounds information at all, so checking was impossible. That part at least intersects with the desire to track certain optimization decisions. Thanks, Florian
