From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Stam Markianos-Wright <Stam.Markianos-Wright@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Richard Sandiford <Richard.Sandiford@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
"nickc@redhat.com" <nickc@redhat.com>
Subject: Re: [GCC][PATCH][ARM] Add Bfloat16_t scalar type, vector types and machine modes to ARM back-end [2/2]
Date: Mon, 13 Jan 2020 10:58:00 -0000 [thread overview]
Message-ID: <152f68a1-45b9-a60b-2c30-f9651b427c4a@foss.arm.com> (raw)
In-Reply-To: <fa4c7602-2735-fb2f-a017-df9b1a38cc22@arm.com>
Hi Stam,
On 1/10/20 6:47 PM, Stam Markianos-Wright wrote:
> Hi all,
>
> This patch is part 2 of Bfloat16_t enablement in the ARM back-end.
>
> This new type is constrained using target hooks TARGET_INVALID_CONVERSION,
> TARGET_INVALID_UNARY_OP, TARGET_INVALID_BINARY_OP so that it may only
> be used
> through ACLE intrinsics (will be provided in later patches).
>
> Regression testing on arm-none-eabi passed successfully.
>
> Ok for trunk?
Ok.
Thanks,
Kyrill
>
> Cheers,
> Stam
>
>
> ACLE documents are at https://developer.arm.com/docs/101028/latest
> ISA documents are at https://developer.arm.com/docs/ddi0596/latest
>
> Details on ARM Bfloat can be found here:
> https://community.arm.com/developer/ip-products/processors/b/ml-ip-blog/posts/bfloat16-processing-for-neural-networks-on-armv8_2d00_a
>
>
>
>
> gcc/ChangeLog:
>
> 2020-01-10Â Stam Markianos-Wright <stam.markianos-wright@arm.com>
>
> Â Â Â Â Â Â Â * config/arm/arm.c
> Â Â Â Â Â Â Â (arm_invalid_conversion): New function for target hook.
> Â Â Â Â Â Â Â (arm_invalid_unary_op): New function for target hook.
> Â Â Â Â Â Â Â (arm_invalid_binary_op): New function for target hook.
>
> 2020-01-10Â Stam Markianos-Wright <stam.markianos-wright@arm.com>
>
> Â Â Â Â Â Â Â * gcc.target/arm/bfloat16_scalar_typecheck.c: New test.
> Â Â Â Â Â Â Â * gcc.target/arm/bfloat16_vector_typecheck_1.c: New test.
> Â Â Â Â Â Â Â * gcc.target/arm/bfloat16_vector_typecheck_2.c: New test.
>
>
next prev parent reply other threads:[~2020-01-13 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:48 Stam Markianos-Wright
2020-01-13 10:58 ` Kyrill Tkachov [this message]
2020-01-16 16:02 ` Stam Markianos-Wright
2020-05-16 8:49 ` Andreas Schwab
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=152f68a1-45b9-a60b-2c30-f9651b427c4a@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=Stam.Markianos-Wright@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--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).