From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Ekanathan, Saravanan" <Saravanan.Ekanathan@amd.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [PATCH] Fix for PR 14423 - Assembler doesn't recognize fma instructions in bdver2 core
Date: Thu, 09 Aug 2012 13:28:00 -0000 [thread overview]
Message-ID: <CAMe9rOpWm7WpzSnymSojJfhJvhfs0Mn5dZeYmk1v7MpTnRN-ZQ@mail.gmail.com> (raw)
In-Reply-To: <8CCF65FBE54B884C85A7D47EBF0834C799EB48@storexdag01.amd.com>
On Thu, Aug 9, 2012 at 1:14 AM, Ekanathan, Saravanan
<Saravanan.Ekanathan@amd.com> wrote:
> Hi,
> The files (arch-10.s and x86-64-arch-2.s) already does fma testing but it doesn't test whether a specific core (bdver2) supports fma or not.
> Re-using these assembly files and creating new .d(objdump) files with -march=bdver2 will not help, because these files have un-supported bdver2 instructions.
>
> So, is there a way to test a core against one/all of the supported instructions in the existing Assembler test framework?
> If not, adding a new testscase for this bug is the only option I guess.
> Regards,
> Saravanan
>
You can create new *.d files, similar to
arch-10-lzcnt.d/x86-64-arch-2-lzcnt.d, with
-march=bdver2+....
--
H.J.
next prev parent reply other threads:[~2012-08-09 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 10:47 Ekanathan, Saravanan
2012-08-06 17:07 ` H.J. Lu
2012-08-07 7:09 ` Ekanathan, Saravanan
2012-08-07 15:48 ` H.J. Lu
2012-08-09 10:11 ` Ekanathan, Saravanan
2012-08-09 13:28 ` H.J. Lu [this message]
2012-08-10 6:48 ` Ekanathan, Saravanan
2012-08-10 16:45 ` H.J. Lu
2012-08-10 20:27 ` Ekanathan, Saravanan
2012-08-10 20:56 ` H.J. Lu
2012-08-10 21:20 ` Ekanathan, Saravanan
2012-08-10 21:42 ` 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=CAMe9rOpWm7WpzSnymSojJfhJvhfs0Mn5dZeYmk1v7MpTnRN-ZQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=Saravanan.Ekanathan@amd.com \
--cc=binutils@sourceware.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).