From: Andrew Cagney <ac131313@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] V850 patch
Date: Thu, 20 Feb 2003 12:57:00 -0000 [thread overview]
Message-ID: <3E54D1CC.3020108@redhat.com> (raw)
In-Reply-To: <1045718178.3918.64.camel@Dragon>
> I'm submitting this for Jim Wilson. It is a revised patch
> of the one submitted by Miles Bader for GDB PR #870.
>
> I have verified it applies cleanly to the current CVS head and
> seems to fix the problems it claims. There are no testsuite regressions.
>
> 2003-01-08 Miles Bader <miles@gnu.org>
> Jim Wilson <wilson@redhat.com>
>
> * v850-tdep.c (v850_scan_prologue): Handle six byte instructions.
> Correctly sign-extend insn2. Use insn2 as well as insn to recognize
> insns where appropriate (some insns only differ in the second 16-bit
> word). Handle mov imm5,r12 and mov imm32,r12.
>
FYI, while Jim has an assignment. Miles doesn't :-( Do you know how
`revised' it is?
Andrew
next prev parent reply other threads:[~2003-02-20 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 5:16 Martin M. Hunt
2003-02-20 12:57 ` Andrew Cagney [this message]
2003-02-20 19:13 ` Martin M. Hunt
2003-02-21 21:40 ` Andrew Cagney
2003-02-21 21:42 ` Andrew Cagney
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=3E54D1CC.3020108@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hunt@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