public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: hjl@nynexst.com (H.J. Lu)
To: dj@stealth.ctron.com (DJ Delorie)
Cc: gas2@cygnus.com, masaki@eie.minolta.co.jp
Subject: Re: [masaki@eie.monolta.co.jp: GAS bug and etc]
Date: Fri, 11 Nov 1994 06:28:00 -0000	[thread overview]
Message-ID: <9411111426.AA05475@titanic.nynexst.com> (raw)
In-Reply-To: <9411111413.AA08124@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.

Thanks.

H.J.
-----
Thu Mar 31 19:34:08 1994  Ken Raeburn  (raeburn@cujo.cygnus.com)

	* i386.h (IS_JUMP_ON_ECX_ZERO, "jcxz" pattern): Operand size
	  prefix is 0x66, not 0x67.  Patch from H.J. Lu (hlu@nynexst.com). 
------
> 
> 
> Return-Path: <masaki@eie.minolta.co.jp>
> Date: Fri, 11 Nov 1994 14:27:09 +0900
> To: djgpp@sun.soe.clarkson.edu
> From: masaki@eie.monolta.co.jp (Kenji  Masaki)
> X-Sender: masaki@vivid.eie.minolta.co.jp
> Subject: GAS bug and etc
> Mime-Version: 1.0
> Content-Type: text/plain; charset=iso-2022-jp
> X-Mailer: Eudora-J(1.3.7-J12)
> DJ-Mail-Sort: djgpp@, djgpp
> 
> Hello.^[$B!!^[(BDJ and evrybody
> 
> We (members of FETX at Niftyserve in JAPAN) found a bug of GAS 2.3 , 2.5.1
> and 2.5.2 ,and FIX it as follows.
> 
> By the way, it seems that treatment of long-filename lacks unity in djgpp.
> i.e. _fixpath is called in stat(), while DPMI(DOS) function [is] called 
> directry in access.c.  Shouldn't it be standardized?
> 
>         
> diff --context=2 -r c:/binutils.2/include/opcode/i386.h
> d:/binutils.2/include/opcode/i386.h
> *** c:/binutils.2/include/opcode/i386.h        Thu Mar 31 16:35:32 1994
> --- d:/binutils.2/include/opcode/i386.h        Wed Nov  9 15:44:48 1994
> ***************
> *** 324,332 ****
>   /* these turn into pseudo operations when disp is larger than 8 bits */
>   #define IS_JUMP_ON_CX_ZERO(o) \
> !   (o == 0x66e3)
>   #define IS_JUMP_ON_ECX_ZERO(o) \
>     (o == 0xe3)
>   
> ! {"jcxz", 1, 0x66e3, _, JumpByte, { Disp, 0, 0} },
>   {"jecxz", 1, 0xe3, _, JumpByte, { Disp, 0, 0} },
>   --- 324,332 ----
>   /* these turn into pseudo operations when disp is larger than 8 bits */
>   #define IS_JUMP_ON_CX_ZERO(o) \
> !   (o == 0x67e3)   /* by members of FEXT niftyserve */
>   #define IS_JUMP_ON_ECX_ZERO(o) \
>     (o == 0xe3)
>   
> ! {"jcxz", 1, 0x67e3, _, JumpByte, { Disp, 0, 0} }, /* by members of FEXT
> niftyserve */
>   {"jecxz", 1, 0xe3, _, JumpByte, { Disp, 0, 0} },
>   
> ---------- Kenji Masaki
> ------------------------------
>     Kenji  Masaki^[$B!!^[(B
> ^[$B!!^[(B  Image Infomation Engineering
>      Division
>    MINOLTA  Co. Ltd. , JAPAN   
> ------------------------------


  reply	other threads:[~1994-11-11  6:28 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 [this message]
1994-11-11  6:37   ` DJ Delorie
1994-11-11  6:45     ` H.J. Lu
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=9411111426.AA05475@titanic.nynexst.com \
    --to=hjl@nynexst.com \
    --cc=dj@stealth.ctron.com \
    --cc=gas2@cygnus.com \
    --cc=masaki@eie.minolta.co.jp \
    /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).