The MSP430 ABI supports build attributes for specifying
the ISA, code model, data model and enum size in ELF object files.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This patch relies on https://reviews.llvm.org/D107968, hence the patch application failure.
Is there a way to link these patches in some way? I've added that revision as a parent of this revision.
Thanks,
Jozef
I don't have commit access, so if this patch is OK, I would appreciate if some would apply it for me.
Thanks.
We generally test new llvm-readelf features with dedicated llvm-readelf tests, usually with the support of yaml2obj or failing that, llvm-mc to generate the input files, where possible. I've no understanding of the attribute section myself, so don't know if either of these are practical options or not, but they would be preferred if so.
Added yaml2obj tests that create SHT_MSP430_ATTRIBUTES sections by
directly specifying the raw contents of the section.
I've kept the CodeGen tests to ensure that we have coverage that the different
values for -mcpu= each emit the expected build attributes.
The ELFDumper.cpp changes have been refactored to apply cleanly on top of the
changes in https://reviews.llvm.org/D107968.
Thanks,
Jozef
Looks reasonable to me, barring some nits. It would be worth @asl or someone else with MSP430 knowledge to take a brief look at the test.
llvm/test/tools/llvm-readobj/ELF/MSP430/build-attributes.test | ||
---|---|---|
24 | Small nit: use - rather than _ in prefix names: it's more common in other tests, and is easier to type on a typical English keyboard. | |
85 | Nit: add a blank line immediately before the YAML blocks. This just makes it a little easier to spot the end of the test directives and start of the YAML for a given test case. |
Ping.
If the added yaml2obj test is acceptable, I would appreciate it if someone would "arc land" the patch for me, as I do not have commit access.
Thanks,
Jozef
Hi @jozefl,
The general assumption in LLVM is that someone has commit access to land their own work after an LGTM on the patch has been received, unless they specifically say so. Also, I personally don't use "arc" for landing patches, so I'll need your preferred email address and name for the commit message if you want me (or someone else) to land it for you. Alternatively, if you've already contributed a few patches, you can request commit access for yourself.
Hi @jhenderson,
It would be much appreciated if you could apply the patch for me, the name and email to use is "Jozef Lawrynowicz <jozefl.opensrc@gmail.com>".
This would only be my second commit to LLVM, but once it's applied I'll try applying for commit access.
Thanks!
Jozef
Actually, I'd still like @asl to take a look at the test, since they presumably have more understanding of this area than I do. Sorry about that.
Small nit: use - rather than _ in prefix names: it's more common in other tests, and is easier to type on a typical English keyboard.