On 11/13/2015 11:36 AM, Wilco Dijkstra wrote:
Evandro Menezes wrote:
Hi, Wilco.
It looks good to me, but FCMP is quite different from FCCMP on Exynos M1,
so it'd be helpful to have distinct types for them. Say, "fcmp{s,d}"
and "fccmp{s,d}". Would it be acceptable to add this with this patch or
On Sat, Nov 14, 2015 at 1:36 AM, Wilco Dijkstra wrote:
>> Evandro Menezes wrote:
>> Hi, Wilco.
>>
>> It looks good to me, but FCMP is quite different from FCCMP on Exynos M1,
>> so it'd be helpful to have distinct types for them. Say, "fcmp{s,d}"
>> and "fccmp{s,d}". Would it be acceptable to add
> Evandro Menezes wrote:
> Hi, Wilco.
>
> It looks good to me, but FCMP is quite different from FCCMP on Exynos M1,
> so it'd be helpful to have distinct types for them. Say, "fcmp{s,d}"
> and "fccmp{s,d}". Would it be acceptable to add this with this patch or
> later?
It would be easy to add f
Hi, Wilco.
It looks good to me, but FCMP is quite different from FCCMP on Exynos
M1, so it'd be helpful to have distinct types for them. Say, "fcmp{s,d}"
and "fccmp{s,d}". Would it be acceptable to add this with this patch or
later?
Thank you.
--
Evandro Menezes
On 11/13/2015 10:02 AM, Wi
This patch adds support for FCCMP. This is trivial with the new CCMP
representation - remove the restriction of FP in ccmp.c and add FCCMP
patterns. Add a test to ensure FCCMP/FCCMPE are emitted as expected.
OK for commit?
ChangeLog:
2015-11-13 Wilco Dijkstra
* gcc/ccmp.c (ccmp_candid
