public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
	Matthew Wahab	<matthew.wahab@foss.arm.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>, nd	<nd@arm.com>,
	"nickc@redhat.com" <nickc@redhat.com>,
	Richard Earnshaw	<Richard.Earnshaw@arm.com>,
	Ramana Radhakrishnan	<Ramana.Radhakrishnan@arm.com>
Subject: RE: [ARM] Enable FP16 vector arithmetic operations.
Date: Tue, 16 May 2017 14:45:00 -0000	[thread overview]
Message-ID: <VI1PR0801MB20310BC9B72E430DCF6F7D12FFE60@VI1PR0801MB2031.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAKdteOaov3BxjczoaEm+R7VoqWxtMmM+5MQR5OoN=1E6F9cMVQ@mail.gmail.com>

Hi Christoph,

> > Thanks, bootstrapped and regtested now on arm-none-linux-gnueabihf
> and no issues.
> > I'll go ahead and commit then.
> >
> 
> One of the new tests fails on arm-none-linux-gnueabi (non-hf) targets:
> FAIL:    gcc.target/arm/armv8_2-fp16-neon-2.c scan-assembler-times
> vceq\\.f16\\td[0-9]+, d[0-0]+, #0 1
> 
> For instance when configured --with-cpu=cortex-a9.
> 

Thanks, I'm making a non-hf build now to fix it.

Tamar

> Christophe
> 
> 
> > Regards,
> > Tamar
> >
> >>
> >> Thanks,
> >> Kyrill
> >>
> >> > Tamar
> >> > ________________________________________
> >> > From: gcc-patches-owner@gcc.gnu.org <gcc-patches-
> owner@gcc.gnu.org>
> >> on
> >> > behalf of Matthew Wahab <matthew.wahab@foss.arm.com>
> >> > Sent: Friday, September 23, 2016 4:02 PM
> >> > To: gcc-patches
> >> > Subject: [ARM] Enable FP16 vector arithmetic operations.
> >> >
> >> > Hello,
> >> >
> >> > Support for the ARMv8.2-A FP16 NEON arithmetic instructions was
> >> > added using non-standard names for the instruction patterns. This
> >> > was needed because the NEON floating point semantics meant that
> >> > their use by the compiler for HFmode arithmetic operations needed to
> be restricted.
> >> > This follows the implementation for 32-bit NEON intructions.
> >> >
> >> > As with the 32-bit instructions, the restriction on the HFmode
> >> > operation can be lifted when -funsafe-math-optimizations is enabled.
> >> > This patch does that, defining the standard pattern names addhf3,
> >> > subhf3, mulhf3 and fmahf3.
> >> >
> >> > This patch also updates the NEON intrinsics to use the arithmetic
> >> > operations when -ffast-math is enabled. This is to make keep the
> >> > 16-bit support consistent with the 32-bit supportd. It is needed so
> >> > that code using the f16 intrinsics are subject to the same
> >> > optimizations as code using the f32 intrinsics would be.
> >> >
> >> > Tested for arm-none-linux-gnueabihf with native bootstrap and make
> >> > check on ARMv8-A and for arm-none-eabi and armeb-none-eabi with
> >> > cross-compiled make check on an ARMv8.2-A emulator.
> >> >
> >> > Ok for trunk?
> >> > Matthew
> >> >
> >> > gcc/
> >> > 2016-09-23  Matthew Wahab  <matthew.wahab@arm.com>
> >> >
> >> >         * config/arm/arm_neon.h (vadd_f16): Use standard arithmetic
> >> >         operations in fast-math mode.
> >> >         (vaddq_f16): Likewise.
> >> >         (vmul_f16): Likewise.
> >> >         (vmulq_f16): Likewise.
> >> >         (vsub_f16): Likewise.
> >> >         (vsubq_f16): Likewise.
> >> >         * config/arm/neon.md (add<mode>3): New.
> >> >         (sub<mode>3): New.
> >> >         (fma:<VH:mode>3): New.  Also remove outdated comment.
> >> >         (mul<mode>3): New.
> >> >
> >> > testsuite/
> >> > 2016-09-23  Matthew Wahab  <matthew.wahab@arm.com>
> >> >
> >> >         * gcc.target/arm/armv8_2-fp16-arith-1.c: Expand comment.
> Update
> >> >         expected output of vadd, vsub and vmul instructions.
> >> >         * gcc.target/arm/armv8_2-fp16-arith-2.c: New.
> >> >         * gcc.target/arm/armv8_2-fp16-neon-2.c: New.
> >> >         * gcc.target/arm/armv8_2-fp16-neon-3.c: New.
> >

  reply	other threads:[~2017-05-16 14:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 15:11 Matthew Wahab
2017-05-02 14:50 ` Tamar Christina
2017-05-15  8:32   ` Tamar Christina
2017-05-15  8:59   ` Kyrill Tkachov
2017-05-16  8:57     ` Tamar Christina
2017-05-16 13:40       ` Christophe Lyon
2017-05-16 14:45         ` Tamar Christina [this message]
2017-05-16 16:10         ` Tamar Christina

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=VI1PR0801MB20310BC9B72E430DCF6F7D12FFE60@VI1PR0801MB2031.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@foss.arm.com \
    --cc=matthew.wahab@foss.arm.com \
    --cc=nd@arm.com \
    --cc=nickc@redhat.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).