On Wed, 2005-06-08 at 19:20 -0700, Stephen Horner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18:00, Mon 06 Jun 05, Tres Melton wrote:
> > Well, the pages I was reading used the nop trick but it looks like a
> > better solution has been presented. I almost forgot that integers are
> > still 32 bit on x86-64 so explaining the movl instead of movq. For
> > those interested the "gcc -S" is (the #APP/#NO_APP is gcc's way of
> > marking inline asm):
> >
> > --------- 8< ----------
> > #APP
> > startit:
> > #NO_APP
> > movl $10, -20(%rbp)
> > #APP
> > stopit:
> > #NO_APP
> > --------- >8 ----------
>
> Forgive me if this seems obvious to most, but i'm unclear on exactly what you
> are saying here about #APP and #NO_APP in regards to labelling assembly code.
> I'm very new to assembly, and this sounded to interesting for me to just say
> to
> myself "meh i'll prolly learn it later . . ." ^_^ Also I was curious why if
> you
> simply intend to lable a code block before assembly, that you don't just
> asm(";;;; pants on ;;;;"); if asm() allows for such a thing ( couldn't find
> man
> 2 asm lol ). At any rate, thanks in advance.
>
First, any blocks of asm("[statements]" [outputs] : [inputs] :
[clobbers] ); that gcc encounters will be placed between #APP and
#NO_APP. Second Mike's "startit:" and "stopit:" are labels or jump
destinations and as such they must be one word (no spaces, dashes, etc.)
but consume no space (except within the intermediate files).
HTH,
--
Tres
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
