4 ms·

This is really cool! I have a question for people who know this stuff: what's the "f.▼ä" pattern that appears at the end of these binaries? It looks intriguing.

• jart 4y ago
  That's a fat nop, or cs nopw 0x0(%rax,%rax,1) to be precise. .byte 0x66,0x2e,0x0f,0x1f,0x84,0x00,0x00,0x00 # f.▼ä .byte 0x00,0x00 ld.bfd uses them to fill empty spaces. See also `o//tool/decode/x86opinfo.com 66 2e 0f 1f 84 00 00 00 00 00` and https://justine.lol/dox/modrm.txt https://justine.lol/dox/modrm.txt and https://justine.lol/dox/geek.txt https://justine.lol/dox/geek.txt
  • dietr1ch 4y ago
    Why is so much padding needed? Once I remove support for Windows and Bare Metal it seems that it might be possible to halve the binary size if you can remove the legal section (or at least change it for a link + checksum?) and the padding. BTW, once I enable windows I think there's padding at the end of the binary section that's hard to notice, it might be good to replace it with something visible. I think it's coming from `ape_idata_iatend`.