From: Joel Brobecker <brobecker@adacore.com>
To: Simon Dardis <Simon.Dardis@imgtec.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: FW: [PATCH, MIPS, PING] Move encoded as 'or' in binutils.
Date: Wed, 28 Oct 2015 19:38:00 -0000 [thread overview]
Message-ID: <20151028165542.GD4009@adacore.com> (raw)
In-Reply-To: <B83211783F7A334B926F0C0CA42E32CA0101F2B9@hhmail02.hh.imgtec.org>
> Sorry, should have followed this up earlier. Can either of you commit on my
> behalf?
Pushed!
> > -----Original Message-----
> > From: Maciej W. Rozycki [mailto:macro@linux-mips.org]
> > Sent: 01 October 2015 08:47
> > To: Joel Brobecker
> > Cc: Simon Dardis; gdb-patches@sourceware.org
> > Subject: Re: FW: [PATCH, MIPS, PING] Move encoded as 'or' in binutils.
> >
> > On Wed, 30 Sep 2015, Joel Brobecker wrote:
> >
> > > > > A recently submitted patch ( http://sourceware.org/ml/binutils/2015-
> > 07/msg00376.html ) to binutils will be encoding move as an 'or' instruction
> > over [d]addu in assembly and various code stubs. This patch for gdb
> > addresses that change for the mips specific parts of gdb.
> > > >
> > > > http://sourceware.org/ml/gdb-patches/2015-07/msg00944.html
> > >
> > > Sorry for the delay. I don't know much about mips, so I will trust you
> > > on the instruction encoding. Patch looks good to me.
> >
> > Encodings look good to me too, thanks!
> >
> > Maciej
--
Joel
prev parent reply other threads:[~2015-10-28 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 12:17 Simon Dardis
2015-09-30 23:18 ` Joel Brobecker
2015-10-01 7:46 ` Maciej W. Rozycki
2015-10-27 15:55 ` Simon Dardis
2015-10-28 19:38 ` Joel Brobecker [this message]
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=20151028165542.GD4009@adacore.com \
--to=brobecker@adacore.com \
--cc=Simon.Dardis@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.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