From: peter w krause <wklux@yahoo.co.uk>
To: linux-assembly@vger.kernel.org
Subject: Re: gas jump
Date: Mon, 1 Sep 2003 10:24:36 +0100 [thread overview]
Message-ID: <200309011024.36769.wklux@yahoo.co.uk> (raw)
In-Reply-To: <3F52FEE9.220376C1@wp.pl>
Maciej Hrebien am Montag, 1. September 2003 09:10:
> > correct code would be:
> > jmp 1f
> > ...
> > 1f:
>
> ^^^^^^
>
> It's "one forward", so the label should be named just "1" without the
> "f". Don't you think? The semantics for such local symbols is N: where N
certainly! 'typing error' :)
hp
--
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml
>> hp -at- lxhp -dot- in-berlin -dot- de <<
next prev parent reply other threads:[~2003-09-01 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 11:06 gas jump peter w krause
2003-09-01 8:10 ` Maciej Hrebien
2003-09-01 9:24 ` peter w krause [this message]
2003-09-03 8:45 ` Maciej Hrebien
2003-09-03 11:54 ` peter w krause
2003-09-03 22:22 ` Maciej Hrebien
-- strict thread matches above, loose matches on Subject: below --
2003-08-30 22:46 Fekete Gabor
2003-08-31 9:38 ` Maciej Hrebien
2003-08-31 9:55 ` Maciej Hrebien
2003-09-01 3:42 ` Rick Hohensee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309011024.36769.wklux@yahoo.co.uk \
--to=wklux@yahoo.co.uk \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).