From: "Meissner, Michael" <michael.meissner@amd.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sourceware.org, gnu@the-meissners.org,
"rajagopal, dwarak" <dwarak.rajagopal@amd.com>
Subject: RE: Patches to add new instructions for a future AMD processor ( AMDFAM10) to the assember
Date: Tue, 11 Jul 2006 16:21:00 -0000 [thread overview]
Message-ID: <6096959DEF5C9447A6BF80BDC7EB9EDC02A449EC@SBOSEXMB1.amd.com> (raw)
In-Reply-To: <20060711005030.GA11398@lucon.org>
We didn't have it in the framework, but that is a good point. We will
do it. Thanks for the reminder.
--
Michael Meissner
AMD, MS 83-29
90 Central Street
Boxborough, MA 01719
> -----Original Message-----
> From: H. J. Lu [mailto:hjl@lucon.org]
> Sent: Monday, July 10, 2006 8:51 PM
> To: Meissner, Michael
> Cc: binutils@sourceware.org; gnu@the-meissners.org; rajagopal, dwarak
> Subject: Re: Patches to add new instructions for a future AMD
processor (
> AMDFAM10) to the assember
>
> On Mon, Jul 10, 2006 at 07:39:55PM -0400, Michael Meissner wrote:
> > Enclosed is a patch to the assembler and disassembler to add the new
> > instructions for a future AMD processor to the GNU assembler and
> > disassembler. I have checked this by building the Linux kernel
2.6.17.4
> > and booting it with no problem. I will commit the changes tomorrow,
> > unless there are some objections. The patch was written by my
> > employee Dwarakanath Rajagopal.
>
> Do you have some testcases to verify that assembler/disassembler work
> on those new instructions correctly?
>
>
> H.J.
next prev parent reply other threads:[~2006-07-11 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 23:59 Michael Meissner
2006-07-11 0:50 ` H. J. Lu
2006-07-11 16:21 ` Meissner, Michael [this message]
2006-07-11 18:24 ` H. J. Lu
2006-07-11 18:28 ` Meissner, Michael
2006-07-11 18:37 ` Khem Raj
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=6096959DEF5C9447A6BF80BDC7EB9EDC02A449EC@SBOSEXMB1.amd.com \
--to=michael.meissner@amd.com \
--cc=binutils@sourceware.org \
--cc=dwarak.rajagopal@amd.com \
--cc=gnu@the-meissners.org \
--cc=hjl@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).