/g/ - why doesn't assembly language have a parse tree? - Technology

Anonymous

09/03/25(Wed)10:32:03 No.106473125

File: Th155Doremy2.png (386 KB, 591x662)

386 KB PNG

Anonymous 09/03/25(Wed)10:32:03 No.106473125 Archived

why doesn't assembly language have a parse tree?

Anonymous
09/03/25(Wed)10:34:07 No.106473142

Anonymous 09/03/25(Wed)10:34:07 No.106473142

wdym

Anonymous
09/03/25(Wed)10:35:33 No.106473150

Anonymous 09/03/25(Wed)10:35:33 No.106473150

>>106473125
There isn't any part of it that's tree-like.

Anonymous
09/03/25(Wed)10:35:36 No.106473151

Anonymous 09/03/25(Wed)10:35:36 No.106473151

File: Sakuya2.jpg (127 KB, 850x1247)

127 KB JPG

>>106473125
ASTs are bloat

Anonymous
09/03/25(Wed)10:52:14 No.106473327

Anonymous 09/03/25(Wed)10:52:14 No.106473327

file ::= (label | instruction)+

label ::= id ':'

instruction ::= mnemonic(op (op)?)?

mnemonic::= id
op ::= id // todo add different op types

Anonymous
09/03/25(Wed)10:57:09 No.106473375

Anonymous 09/03/25(Wed)10:57:09 No.106473375

>>106473150
why not? also what about [1+2*rax]

Anonymous
09/03/25(Wed)11:09:25 No.106473485

Anonymous 09/03/25(Wed)11:09:25 No.106473485

>>106473327
how do you accomidate affixes? cisc assembly isn't an isolating language like most formal languages, it's polysynthetic. operands can have (restricted) arithmetic expressions, and instructions can have suffixes and infixes. also you haven't accounted for pointer dereferencing, non-instruction directives, literals, segments, etc.

Anonymous
09/03/25(Wed)11:29:47 No.106473658

Anonymous 09/03/25(Wed)11:29:47 No.106473658

>>106473375
Those expressions are parsed by the assembler, encoded and then promptly discarded.

Anonymous
09/03/25(Wed)14:18:00 No.106475141

Anonymous 09/03/25(Wed)14:18:00 No.106475141

>>106473485
I'm pretty sure that anon wasn't intending his post to be comprehensive.