Thinking a bit more about it, I reckon we can't just generally generally 
entries in the
.eh_table if a function does not have CFI instructions as we'd need at least two
kinds of "empty" unwind info: one for frames where unwinding is no longer 
possible,
and one where unwinding is done using just the initial CFI instructions (e.g. 
functions
without a frame/frame pointer/CSR saves).

In that sense,  creating .eh_frame entries for outlined functions is correct. 
However, if
outlined functions do not contain CFI instructions, I think we can take the hit
on the quality of the debugging information or the precision of profiling for 
the
`-Oz` case only, for the benefit of the code size.

~chill
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org

Reply via email to