From: Kazuhiro Inaoka <inaoka.kazuhiro@renesas.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "binutils@sources.redhat.com" <binutils@sources.redhat.com>,
"cgen@sources.redhat.com" <cgen@sources.redhat.com>
Subject: [PATCH] m32r-*-as bad instruction 'seth r0, #shigh(0xffff8000)'
Date: Mon, 29 Mar 2004 08:48:00 -0000 [thread overview]
Message-ID: <4067E291.4070002@renesas.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Hello,
This is a patch to fix the following bug.
Command line:
m32r-linux-as -o tt.o tt.s
or
m32r-elf-as -o tt.o tt.s
pattern is:
.section .text
seth r0, #shigh(0xffff8000)
.end
Error log is:
tt.s: Assembler messages:
tt.s:2: Error: bad instruction 'seth r0,#shigh(0xffff8000)'
Please commit it and regenerate opcodes/m32r-asm.c.
Regards,
Kazuhiro Inaoka
ChangeLog:
2004-03-29 Kazuhiro Inaoka < inaoka dot kazuhiro at renesas dot com >
* cpu/m32r.opc (parse_hi16): Fixed shigh(0xffff8000) bug.
[-- Attachment #2: m32r.opc.patch --]
[-- Type: text/plain, Size: 780 bytes --]
Index: m32r.opc
===================================================================
RCS file: /cvs/src/src/cpu/m32r.opc,v
retrieving revision 1.2
diff -c -r1.2 m32r.opc
*** m32r.opc 23 Feb 2004 16:46:46 -0000 1.2
--- m32r.opc 29 Mar 2004 08:09:53 -0000
***************
*** 153,159 ****
++*strp;
if (errmsg == NULL
&& result_type == CGEN_PARSE_OPERAND_RESULT_NUMBER)
! value = (value >> 16) + (value & 0x8000 ? 1 : 0);
*valuep = value;
return errmsg;
}
--- 153,162 ----
++*strp;
if (errmsg == NULL
&& result_type == CGEN_PARSE_OPERAND_RESULT_NUMBER)
! {
! value = value + (value & 0x8000 ? 0x10000 : 0);
! value >>= 16;
! }
*valuep = value;
return errmsg;
}
next reply other threads:[~2004-03-29 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 8:48 Kazuhiro Inaoka [this message]
2004-03-30 9:29 ` Nick Clifton
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=4067E291.4070002@renesas.com \
--to=inaoka.kazuhiro@renesas.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=nickc@redhat.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).