From: kevin lyda (kevin at domain suberic.net)
Date: Wed 15 Aug 2001 - 15:53:51 IST
On Wed, Aug 15, 2001 at 03:34:02PM +0100, Dave Airlie wrote:
> On Wed, 15 Aug 2001, jac1 wrote:
> > On the subject of assembly code, why is linux's inline asm code so goddamn
> > cryptic to follow? Is there an advantage to it? Microsoft's inline __asm {} is
> > soooooo much easier to read + use.
> What do you mean Linux users asm {} as well it's just in the kernel that
> MACROs and "\n\t " stuff is in there... the \n\t stuff is useful if you
> are actually using inline assembly and reading listing files.. it makes
> stuff come out on different line numbers ... it's a bitch for reading
> however..
huh? you mean there's a problem with:
opcode1 a1, a2...
oc2 a1, a2...
oc3 ...
label:
oc4 ...
that's how i was taught to write assembly (vax, dg aviion, sparc)[0].
there's another way? how else would you do it?
kevin
[0] circa 1990 or so. yes we had invented fire by then, you're confusing
me with niall.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:11:40 GMT