public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org, 	Sergey Ilyevsky <silyevsk@gmail.com>
Subject: Re: [PR 2494] PDP-11: Wrong opcode for SEC/CLC
Date: Fri, 31 Mar 2006 14:56:00 -0000	[thread overview]
Message-ID: <20060331120017.GK22210@lug-owl.de> (raw)
In-Reply-To: <20060331114603.GC22279@bubble.grove.modra.org>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On Fri, 2006-03-31 21:16:03 +0930, Alan Modra <amodra@bigpond.net.au> wrote:
> On Fri, Mar 31, 2006 at 01:21:11PM +0200, Jan-Benedict Glaw wrote:
> > > > -  { "sec",     0x00a1, 0xffff, PDP11_OPCODE_NO_OPS,    PDP11_BASIC },
> > > > +  { "sec",     0x00b1, 0xffff, PDP11_OPCODE_NO_OPS,    PDP11_BASIC },
> > 
> > May I check this in under the obvious rule?
> 
> Yes, that would have been OK, but someone else posted a patch before
> this one, which I've committed.

*gnarf*  So we had a nice overlap and no hint in the PR. However, the
bug is fixed, so everything is okay again :-)

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 für einen Freien Staat voll Freier Bürger"  | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-03-31 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 11:12 Jan-Benedict Glaw
2006-03-31 11:21 ` Sergey Ilyevsky
2006-03-31 11:44   ` Jan-Benedict Glaw
2006-03-31 12:00     ` Alan Modra
2006-03-31 14:56       ` Jan-Benedict Glaw [this message]
2006-03-31 15:03         ` Paul Koning
2006-03-31 15:57           ` Jan-Benedict Glaw

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=20060331120017.GK22210@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=silyevsk@gmail.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).