Live data from Hacker News

x86 architecture 1 byte opcodes

sandpile.org

11–20 of 35 posts

Re: x86 architecture 1 byte opcodes

#11
post #10

I don't understand, without further description of the symbols.

Not sure why you're being downvoted. You need a to know quite a bit of esoteric knowledge to parse this beyond knowing x86 opcodes (even x86 assembly). It's more or less the same information you get from the intel manuals (specifically appendix 2A of https://www.intel.com/content/www/us/en/developer/articles/t... ). There you can also see what e.g. "Jb" means (a byte sized immediate following the instruction that spe…

>Not sure why you're being downvoted.

I downvote people when they say they don't know what something is when they could have used a LLM to explain it to them.

Re: x86 architecture 1 byte opcodes

#12
post #10

Earlier quoted context omitted.

Not sure why you're being downvoted. You need a to know quite a bit of esoteric knowledge to parse this beyond knowing x86 opcodes (even x86 assembly). It's more or less the same information you get from the intel manuals (specifically appendix 2A of https://www.intel.com/content/www/us/en/developer/articles/t... ). There you can also see what e.g. "Jb" means (a byte sized immediate following the instruction that spe…

>Not sure why you're being downvoted. I downvote people when they say they don't know what something is when they could have used a LLM to explain it to them.

What if the LLM gives them bad information and they don't know it? I personally would also just ask in a thread than risk the LLM info.

Re: x86 architecture 1 byte opcodes

#13
post #10

Earlier quoted context omitted.

Not sure why you're being downvoted. You need a to know quite a bit of esoteric knowledge to parse this beyond knowing x86 opcodes (even x86 assembly). It's more or less the same information you get from the intel manuals (specifically appendix 2A of https://www.intel.com/content/www/us/en/developer/articles/t... ). There you can also see what e.g. "Jb" means (a byte sized immediate following the instruction that spe…

>Not sure why you're being downvoted. I downvote people when they say they don't know what something is when they could have used a LLM to explain it to them.

I never punish people for asking a question. It's how you learn!

Re: x86 architecture 1 byte opcodes

#15
post #4

Need a couple of instructions for accessing memory (and possibly loading immediates) but otherwise seems like a perfectly adequate general-purpose instruction set. Might be fun (for some values of "fun") to write a compiler backend for it.

You've always got the stack segment (SS) to play with and there's also:

https://www.felixcloutier.com/x86/xlat:xlatb

Re: x86 architecture 1 byte opcodes

#16
post #10

Earlier quoted context omitted.

Not sure why you're being downvoted. You need a to know quite a bit of esoteric knowledge to parse this beyond knowing x86 opcodes (even x86 assembly). It's more or less the same information you get from the intel manuals (specifically appendix 2A of https://www.intel.com/content/www/us/en/developer/articles/t... ). There you can also see what e.g. "Jb" means (a byte sized immediate following the instruction that spe…

>Not sure why you're being downvoted. I downvote people when they say they don't know what something is when they could have used a LLM to explain it to them.

The link is to an opcode map with strange abbreviations with no apparent explanation. Asking "What am I looking at?" without doing any research (with a LLM or otherwise) is entirely reasonable.

Re: x86 architecture 1 byte opcodes

#18
post #16

Earlier quoted context omitted.

>Not sure why you're being downvoted. I downvote people when they say they don't know what something is when they could have used a LLM to explain it to them.

The link is to an opcode map with strange abbreviations with no apparent explanation. Asking "What am I looking at?" without doing any research (with a LLM or otherwise) is entirely reasonable.

It is entirely reasonable, but these kind of comments are essentially wishing sites could cater to their knowledge level.

It's like complaining that the article is not written in French. It's noise in the comment section of an article. If someone wants such a thing, browsers have functionality to translate pages to French. Not every site needs to have their own French translation to suit such a person.

Re: x86 architecture 1 byte opcodes

#19
post #16

Earlier quoted context omitted.

The link is to an opcode map with strange abbreviations with no apparent explanation. Asking "What am I looking at?" without doing any research (with a LLM or otherwise) is entirely reasonable.

It is entirely reasonable, but these kind of comments are essentially wishing sites could cater to their knowledge level. It's like complaining that the article is not written in French. It's noise in the comment section of an article. If someone wants such a thing, browsers have functionality to translate pages to French. Not every site needs to have their own French translation to suit such a person.

They were not asking for the website to change; they were asking for context so that they can appreciate the website.
Post reply on HN