The output of RISC-V objdump can only be viewed with 8-space tabs which, meh, but what's really great is the 4-nibble instructions have 6 extra spaces after thempic.twitter.com/gJmh48U0Ka
-
Wow. Interesting find. I guess that's because other architectures but a space after each byte and the extra two spaces are to compensate for the two extra byte-separating spaces that are missing in the risc-v objdump output format.
Yep. Commenting out this putchar() from binutils/objdump.c seems to fix it.pic.twitter.com/kNIq2QXWbd
-
-
Neat! Will try that out. Noticed that arm-none-eabi-objdump does not have this issue, and does not have the spaces you mentioned (is that an Intel thing?):pic.twitter.com/NdiZlRyB5R
-
Ah it does insert spaces in 32-bit instructions thoughpic.twitter.com/TfMDhkivHA
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.