Wrote about llvm/lib/MC subproject on https://llvm.org/docs/GettingStarted.html page.
Details
Diff Detail
Event Timeline
I added @arsenm as the second reviewer, If he thinks the patch looks good, we will commit it.
| llvm/docs/GettingStarted.rst | ||
|---|---|---|
| 887 | Saying it translates implies it’s just the assembler and disassembler. It normally directly emits object files | |
Changed the statement that said 'translation of machine instruction, which suggested that it is just assembler or disassembler.
| llvm/docs/GettingStarted.rst | ||
|---|---|---|
| 887–888 | object and text? | |
I didn't understand, can u elaborate plse @arsenm . Does it produce text file as well? it helps in object code emission?
It does both. It's everything related to the presentation and consumption of machine encoding, text and binary
| llvm/docs/GettingStarted.rst | ||
|---|---|---|
| 887 | "It produces machine code object file" sounds grammatically off. files? This also stopped referencing the text assembly emission | |
I think you can copy-paste from here https://llvm.org/docs/CodeGenerator.html#the-mc-layer.
Read a little about this layer under MCInst section here: https://eli.thegreenplace.net/2012/11/24/life-of-an-instruction-in-llvm
MC layer handles the object-file emission (it can also emit textual assembly files).
Saying it translates implies it’s just the assembler and disassembler. It normally directly emits object files