Why does .balign >=8 (or .align >=3) produce weird glitchy behavior? (arm-none-eabi-as)

LanHikari22 / GBA-IDA-Pseudo-Terminal

IDAPython tools to aid with analysis, disassembly and data extraction using IDA python commands, tailored for the GBA architecture at some parts

13 stars 1 forks source link

Why does .balign >=8 (or .align >=3) produce weird glitchy behavior? (arm-none-eabi-as) #9

Open LanHikari22 opened 6 years ago

LanHikari22 commented 6 years ago

the disassembly tools generate .byte 0's and .word 0's whenever they detect an ALIGN n where n is greater than 4. It makes sense that you wouldn't really need to align to anything more than a word in the GBA architecture, but ALIGN 0x10 (or .balign 0x10, 0x00) would modify the data that came before it, instead of padding with zeros