Writing an IR from Scratch and survive to write a post(farena.in)
farena.in
Writing an IR from Scratch and survive to write a post
https://farena.in/compilers/programming/writing-an-ir-from-scratch/
6 comments
I wish authors would include the full form in brackets after the first use of an acronym in a text.
They do so:
“ though the project is discontinued (a new version is being written here Shuriken), I thought it would be interesting to write about my experience of how I wrote the first version of its Intermediate Representation (from now on IR), how I implemented the different algorithms, and how I transformed Dalvik bytecode into this IR”
“ though the project is discontinued (a new version is being written here Shuriken), I thought it would be interesting to write about my experience of how I wrote the first version of its Intermediate Representation (from now on IR), how I implemented the different algorithms, and how I transformed Dalvik bytecode into this IR”
I do that all the time to the point that it makes every acronym a TWoT (total waste of time)
Ohhhhhh. I clicked on this because Scratch was capitalized, and I though "wow, an IR for MIT's Scratch." I'm a little disappointed now.
[deleted]
For some reason when reading the title, I thought infrared instead of intermediate representation.
It also still made a tiny bit of sense in that context since you can easily set stuff on fire with IR laser
It also still made a tiny bit of sense in that context since you can easily set stuff on fire with IR laser
I understood what IR was, but due to the capitalization of the title, I thought it was written in Scratch programming language.
Ha, I read it as Incident Response and was about to read the gory details.
Same here! Although in the context of "Writing" an IR, writing an incident response policy makes the most sense (but isn't very blog worthy)
[deleted](1)
Context: compilers
https://en.wikipedia.org/wiki/Intermediate_representation