From: James E Wilson <wilson@specifixinc.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] ia64 segfault on nop in X-slot of MLX bundle
Date: Thu, 27 Jan 2005 19:55:00 -0000 [thread overview]
Message-ID: <1106855676.18514.2.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <1106797178.12995.81.camel@aretha.corp.specifixinc.com>
On Wed, 2005-01-26 at 19:39, James E Wilson wrote:
> nop.x wasn't in the original architecture. My recollection is that brl
> was added first, and then nop.x was added later, and when that happened,
> we missed the fact that this string needed to change to also allow x
> unit instructions.
Actually, ignore this, I think it is wrong. It is true though that brl
wasn't in the original specification (and isn't implemented in hardware
on the Itanium1), but we did have movl and thus probably had nop.x from
the beginning. Anyways, the point here is that we never tried to
prevent nop.x from working, this was just a simple oversight.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2005-01-27 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 10:35 Jan Beulich
2005-01-27 3:39 ` James E Wilson
2005-01-27 19:55 ` James E Wilson [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=1106855676.18514.2.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=JBeulich@novell.com \
--cc=binutils@sources.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).