Closed TommyMurphyTM1234 closed 7 years ago
Hope it's OK to post this here
Tommy, please use this tracker only for bugs and enhancements; for questions, unless they are of wide audience, please use the project forum.
Now I'm not sure if this data is actually literal pool data in a code section so objdump may know no better than to try to disassemble it? Or if there are some options that the plugin list file generation build step could/should pass to avoid this happening?
my toolchain release includes the gcc manuals. in binutils.pdf there is a separate chapter for objdump, with lots of options, perhaps that would be a good place to start the search.
OK - apologies for that. I'll close this one and raise it on the mailing list or riscv or master binutils pages.
Hope it's OK to post this here at least for initial consideration - I'm not sure if it's actually a plugin issue or something to do with objdump - or maybe simply a misunderstanding on my part.
The GNU RISC-V Cross Create Listing build step calls objdump to generate a list file including disassembly etc. By default the command line is:
objdump --source --all-headers --demangle --line-numbers --wide "riscv-systick-blinky.elf"
However this has the effect of trying to disassemble data as well as code sections. In my case I'm compiling for -march=rv32im -mabi=ilp32 and yet I see this in the list file:
Note the disassembly of data at the end of the file from address 0x80001740 onwards which appears as if it was compressed code.
Now I'm not sure if this data is actually literal pool data in a code section so objdump may know no better than to try to disassemble it? Or if there are some options that the plugin list file generation build step could/should pass to avoid this happening?
Thanks.