X86 mov is turing complete: mov-only compiler

Re:X86 mov is turing complete: mov-only compiler by Buge on Sunday June 21, 2015 @12:23AM (#9752165)

It also uses a single jmp instruction to branch back to the start in a loop.

Two values a and b can be compared by storing 0 into * a and 1 into * b. Then a == b if * a is 1. Then this value can be used to index into an array to provide different behavior based on if a == b.

Edit: apparently HN doesn't allow me to escape * with \, which the markdown spec says I should be able to do.

[ Parent | on HN ]

Re:X86 mov is turing complete: mov-only compiler by thaumasiotes on Sunday June 21, 2015 @12:29AM (#9752181)

> HN doesn't allow me to escape * with \, which the markdown spec says I should be able to do

So? What does the markdown spec have to do with... anything? The XML spec says you have to begin your comment with a version number declaration, but you're not doing that.

[ Parent | on HN ]

Re:X86 mov is turing complete: mov-only compiler by Buge on Sunday June 21, 2015 @01:13AM (#9752286)

I thought it was trying to implement markdown by italicizing half my sentence when I put * in. Markdown was what popped into my mind when I saw that behavior. It would be nice if I could find a way of escaping them without having to insert spaces where I don't want spaces.

[ Parent | on HN ]

Re:X86 mov is turing complete: mov-only compiler by lorenzhs on Sunday June 21, 2015 @07:46AM (#9753037)

There isn't one, HN doesn't use markdown. See https://news.ycombinator.com/formatdoc

[ Parent | on HN ]

Re:X86 mov is turing complete: mov-only compiler by kuschku on Sunday June 21, 2015 @10:30AM (#9753572)

It should use markdown, though.

[ Parent | on HN ]