X86 assembly encounter

http://jan.rychter.com/enblog/2009/12/4/x86-assembly-encounter.html

by jwr • 17 years ago

24 7 17 years ago

jan.rychter.com

docmach• 17 years ago

As I posted in a comment on the article, he seems to have unrealistic expectations for an x86 assembler. TI's DSPs have a nice assembly because of their architecture. The x86 architecture is too complicated and the implementations too diverse to have an assembler like he wants.

tptacek2• 17 years ago

Not so much: http://cr.yp.to/qhasm.html

The version of our Ruby x86 assembler on my desk does register allocation as well.

jwr3• 17 years ago

Cool! This is exactly what I had in mind. I didn't know about this project.

Unfortunately, it seems to have been abandoned...

jwr3• 17 years ago

I'd put it another way: on VLIW DSPs they HAD to provide a good assembler, or they would be too difficult to program. From what I remember on some of them you have to manually manage the pipeline -- e.g. a jump instruction needs to occur several instructions BEFORE the actual jump, because by the time that instruction gets executed, several instruction after it will already have been decoded. You really don't want to do that manually.

The only non-DSP processor I know that required programmers to schedule jumps ahead of time manually was the Intel i860, and it WAS too difficult to program, that's why it disappeared.

yason• 17 years ago

With regard to PSRLB, PSRLW, PMADDUBSW, and PMOVMSKB, I must say I loved assembly much more in the times when each instruction mnemonic was only 2-3 characters.

jwr3• 17 years ago

Oh, the real fun begins with SSE4.2 and things like PCMPISTRM (the whole PCMPxSTRx family), where you not only have the mnemonics, but also an 8-bit immediate with each bit specifying a different aspect of operation for the string comparison engine.

X86 assembly encounter

Related Stories