llvm-readobj support a new option --exception-section for xcoff object file.
https://www.ibm.com/docs/en/aix/7.2?topic=formats-xcoff-object-file-format#XCOFF__iua3i23ajbau
Differential D133030
[AIX] llvm-readobj support a new option --exception-section for xcoff object file. DiggerLin on Aug 31 2022, 8:28 AM. Authored by
Details llvm-readobj support a new option --exception-section for xcoff object file. https://www.ibm.com/docs/en/aix/7.2?topic=formats-xcoff-object-file-format#XCOFF__iua3i23ajbau
Diff Detail
Event Timeline
Comment Actions I did wonder whether this should really just be reusing the existing --unwind option, but as I understand it, the XCOFF exception section isn't really about unwinding the stack or anything along those lines. Is that correct? Rather than canned binaries, I think it wouldn't be too hard to add yaml2obj support for exception sections, so that you can create the input at test time. Your commit message should be a grammatically correct sentence, with leading capital letter (i.e. "Add a new ..."), much like comments. I've not really looked at the XCOFFObjectFile code changes or the testing just yet. Please don't forget to test error/warning paths, to show that the code can handle malformed inputs.
Comment Actions
yes, you are correct, the exception section is not for unwind. so we can not use the --unwind for it.
yes, if I do the yaml2obj first , I need a tools to decode the object file generated by yaml2obj when I add a test for the yaml2obj, but there is not now. My propose is three steps:
Comment Actions address James's comment.
Comment Actions I think my preferred option would be to use yaml2bj/obj2yaml to test each other, with an additional manual step for now:
Comment Actions address comment.
Comment Actions address comment.
Comment Actions One remaining nit, otherwise LGTM.
|
I think you can simplify to the inline suggestion.