I spotted then following lines in objdump output: 4: 0f 94 84 24 20 10 00 sete 0x1020(%esp) b: 00 Instruction 'sete 0x1020(%esp)' is correct, but the following 00 byte still belongs to 'sete' instruction. I believe that the correct fix for all such issues is to make 'as' and 'objdump' to work off the same instruction definitions.
see objdump --help, -w option