From: Alan Modra <amodra@bigpond.net.au>
To: "H.J. Lu" <hongjiu.lu@intel.com>
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] some x86 instructions tagged with incorrect CPU type
Date: Mon, 15 Nov 2004 04:35:00 -0000 [thread overview]
Message-ID: <20041115043500.GM32175@bubble.modra.org> (raw)
In-Reply-To: <s18a024b.060@emea1-mh.id2.novell.com>
On Thu, Nov 04, 2004 at 11:20:37AM +0100, Jan Beulich wrote:
> Various instructions where not tagged with the right required feature
> set
> identifiers, and some CPUs had by default features enabled which they
> don't
> always provide. This tries to rectify this. Additionally, it provides
> the
> ability to add certain feature groups to the user selected CPU (i.e.
> MMX
> instructions with a Pentium CPU).
HJ, would you please review this patch? I figure you have more of a
vested interest in x86 these days than I do..
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2004-11-15 4:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 10:20 Jan Beulich
2004-11-15 4:35 ` Alan Modra [this message]
2004-11-16 19:40 ` H. J. Lu
2004-11-18 16:32 Jan Beulich
2004-11-19 19:33 ` H. J. Lu
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=20041115043500.GM32175@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hongjiu.lu@intel.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).