|Writing my first compiler Yarrago@hotmail.com (2002-03-17)|
|Re: Writing my first compiler email@example.com (Joachim Durchholz) (2002-03-19)|
|Re: Writing my first compiler missoulaleo@DIE_SPAMBOT_DIEearthlink.net (john thrum) (2002-03-19)|
|Re: Writing my first compiler firstname.lastname@example.org (Dobes Vandermeer) (2002-03-21)|
|From:||Joachim Durchholz <email@example.com>|
|Date:||19 Mar 2002 16:13:28 -0500|
|Posted-Date:||19 Mar 2002 16:13:27 EST|
> Is an assembler basically a matter of converting the mnemonics into
> opcodes and linking the file with a header to make it into an
> or is there more to it?
You must produce output that's acceptable to the linker. (Unless, of
course, writing a linker is the next thing you want. In this case, the
will problem shift, it's producing output that's acceptable to the
operating system then.) Either case, the biggest problem is digging
up a recent and accurate description of what you may or may not feed
to the intended target.
Return to the
Search the comp.compilers archives again.