From: hjl@nynexst.com (H.J. Lu)
To: dj@stealth.ctron.com (DJ Delorie)
Cc: gas2@cygnus.com, masaki@eie.minolta.co.jp,
raeburn@cygnus.com (Ken Raeburn)
Subject: Re: [masaki@eie.monolta.co.jp: GAS bug and etc]
Date: Fri, 11 Nov 1994 06:45:00 -0000 [thread overview]
Message-ID: <9411111444.AA05506@titanic.nynexst.com> (raw)
In-Reply-To: <9411111438.AA11089@delorie>
>
> > Your patch jusr reversed what I did. Could you please tell
> > me why I was wrong and you were right? I thought I checked
> > the Intel x86 manual when I fixed that bug.
>
> I didn't try to validate the patch; it was more of an FYI, which is
> why I included the header info. If it's wrong, or you need more info,
> the original sender is the one to talk with (cc'd in both mails).
> Sorry if my intention wasn't clear.
I just hate that, especially when people say my patch is wrong without
doing their homework first :-).
>
> Original sender:
> > From: masaki@eie.monolta.co.jp (Kenji Masaki)
>
> Note that the "jcxz" opcode in the gas that djgpp's libc was built
> with doesn't work as expected - jecxz does. This might have confused
> people into thinking that there was a bug, or maybe there really is
> one. jcxz is the 16-bit version (or pretends to be).
>
jcxz and jecxz are totally different. One checks cx, the other
checks ecx. You have to decide what you want to use.
> Since jcxz uses both a register (opsize?) and an address (addrsize?),
> there may be a need for both prefixes.
I think gas will add a right address prefix automatically when it sees
a large offset. Ken?
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
next prev parent reply other threads:[~1994-11-11 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-11 6:11 DJ Delorie
1994-11-11 6:28 ` H.J. Lu
1994-11-11 6:37 ` DJ Delorie
1994-11-11 6:45 ` H.J. Lu [this message]
1994-11-11 6:49 ` DJ Delorie
1994-11-11 7:06 ` H.J. Lu
1994-11-11 10:31 ` Richard Stallman
1994-11-11 10:46 ` DJ Delorie
1994-11-11 14:27 ` Richard Stallman
1994-11-11 15:01 ` Arthur Kreitman
1994-11-11 13:42 mycroft
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=9411111444.AA05506@titanic.nynexst.com \
--to=hjl@nynexst.com \
--cc=dj@stealth.ctron.com \
--cc=gas2@cygnus.com \
--cc=masaki@eie.minolta.co.jp \
--cc=raeburn@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).