You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel "decompiled code is identical to the assembly code that you wrote" is sligthly misleading. Both MASM and YASM support macros and equates that are inlined during compilation. Thus, any decompilation process will be unable to recover these syntactic constructions.
The text was updated successfully, but these errors were encountered:
BlueSkeye
changed the title
Mod1-Slide12-WyWiWyG
Vol1-Mod1-Slide12-WyWiWyG
Mar 23, 2021
hmm, I will think how to rephrase it to make is less misleading. this is quite nuanced - macros are still representation of some block of instruction in pure assembly, which will be the same in output as they were in the input. and this is what I meant: when we write in the pure assembly: we decide which exact register we want to use, etc. it is not something decided for us by the compiler. and this is something important to highlight.
Ok. You want to emphasis asm = full processor control VS other languages delegating this control to the compiler. If so, my remark about macros is at least useless and could even be confusing for the reader. I suggest you close this issue and forget about macros in your text.
I feel "decompiled code is identical to the assembly code that you wrote" is sligthly misleading. Both MASM and YASM support macros and equates that are inlined during compilation. Thus, any decompilation process will be unable to recover these syntactic constructions.
The text was updated successfully, but these errors were encountered: