> ..what Addressing Modes are.

I'd say, it's only about parsing the syntax.
The registers ( ds, cs , .. ), depending on the architecture,
have to be stored anyways.

Furthermore, I didn't get so close yet,
but the MIPS architecture/assembly seems to be a good target as intermediate language between c and perl.
(according to schmorp, who chose the architecture cause it's simplicity for his emulator
http://blog.schmorp.de/2015-07-01-emulating-linux-mips-in-perl-3.html)

Oh, and I did find the movfuscator,
which "compiles programs into "mov" instructions, and only "mov" instructions. Arithmetic, comparisons, jumps, function calls, and everything else a program needs are all performed through mov operations; there is no self-modifying code, no transport-triggered calculation, and no other form of non-mov cheating."
:)) haven't got the thing to compile yet.
And I can't imagine yet, how this should work at all.

But this would not only solve the problem of addressing the pseudo ram,
it might render the resulting code close to undebuggable.
As long as there is no tool, which translates back into "normal" code.
When this is possible at all.

In reply to Re^4: Interpreting Assembly by misc
in thread Interpreting Assembly by misc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.