OK, let me see if I got this right.... You have made up a listing that
includes the following information when seen in its final form:
instruction name
instruction format
addressing mode
binary/hex equivalent.
If that is the case then congratulations for the stubbornness to complete
the effort--because most of us just look this information up if we so desire
to have it! This is not to say that your effort has been in vain. If you
have actually made up an assembler parser then you may have made something
that is in and of itself quite useful. This would be because we could
instead pre-trap code that may be able to perform undesirable actions. Is
this where you were headed?
Drew Northup, N1XIM
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of [EMAIL PROTECTED]
> Sent: Saturday, October 21, 2000 8:47 PM
> To: [EMAIL PROTECTED]
> Subject: Hi
>
>
> Greetings, everyone. I have just joined this list.\
>
> BTW, I have created a text file that represents the entire non-
> floating point 586 instruction set, in only a few hundered lines. I
> then wrote a program to expand that file to all possible encodings.
>
> I see two good ways to go about doing this: translation and setting
> the code segment limit such that a fault is generated before jump
> instructions to below the code being analysed; keep analysing up to
> the point of conditional jumps to after the code being analysed.
>
> Lemme know if you'd like me to explain this in a way that makes
> sense.
>
> -WS
>
>
>
