On 3 February 2014 17:31, Keith Walker <[email protected]> wrote: > Should the EHABI directives (.fnstart/.fnend/.push/.pad/.setfp etc) > always be generated (and thus resulting in the generation of .ARM.extab & > .ARM.exidx sections), or should these directives only be generated when > there are unwind tables to be described? >
Hi Keith, AFAIK, .ARM.exidx only needs to exist when there is one of more of .ARM.extab, which is only needed if there are functions that need unwinding because of exception handling (C++) code. The fact that we are always generating is probably due to the fact that EHABI was never on by default so it never needed to check if it *should* generate the table or not, and always did. I'll have a look on how to only enable it the function doesn't have nounwind attribute. I don't know the role of -munwind-tables on the attribute, but we should generate them if on. cheers, --renato
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
