From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Evandro Menezes <e.menezes@samsung.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
nd <nd@arm.com>, Andrew Pinski <pinskia@gmail.com>
Subject: Re: [PATCH 2/4 v2][AArch64] Add support for FCCMP
Date: Wed, 06 Jan 2016 12:05:00 -0000 [thread overview]
Message-ID: <AM3PR08MB0088A372287FCB8D106A4DE383F40@AM3PR08MB0088.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <568C3D19.908@samsung.com>
Hi Evandro,
> Here's what I had in mind when I inquired about distinguishing FCMP from
> FCCMP. As you can see in the patch, Exynos is the only target that
> cares about it, but I wonder if ThunderX or Xgene would too.
>
> What do you think?
The new attributes look fine (I've got a similar outstanding change), however
please don't add them to non-AArch64 cores. We only need it for thunderx.md,
cortex-a53.md, cortex-a57.md, xgene1.md and exynos-m1.md.
Wilco
next prev parent reply other threads:[~2016-01-06 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 10:33 Wilco Dijkstra
2015-12-15 16:42 ` James Greenhalgh
2015-12-15 17:20 ` Wilco Dijkstra
2015-12-16 0:08 ` Bernd Schmidt
2016-01-05 22:01 ` Evandro Menezes
2016-01-05 22:05 ` Andrew Pinski
2016-01-06 12:05 ` Wilco Dijkstra [this message]
2016-01-06 20:44 ` Evandro Menezes
2016-01-20 23:10 ` Evandro Menezes
2016-01-21 9:24 ` James Greenhalgh
2016-01-21 11:13 ` Wilco Dijkstra
2016-01-21 12:10 ` James Greenhalgh
2016-01-21 19:58 ` Evandro Menezes
2016-01-21 20:03 ` Evandro Menezes
2016-01-21 22:07 ` James Greenhalgh
2016-01-21 22:55 ` Evandro Menezes
2016-02-03 19:49 ` Evandro Menezes
2016-02-15 10:53 ` James Greenhalgh
2016-02-15 21:20 ` Evandro Menezes
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 16:27 Wilco Dijkstra
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=AM3PR08MB0088A372287FCB8D106A4DE383F40@AM3PR08MB0088.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=e.menezes@samsung.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=pinskia@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).