llvm dev - Sep 2019 - Compile for ARM SVE with the latest LLVM

Renato et al.
In the meantime, is there an out of tree branch I mean, other than LLVM
trunk so I can test how much I can SVE vectorize my code with it?

Arm seemed to gave taken down the GitHub branch for sometime.

On Wed, Sep 11, 2019 at 20:41 Renato Golin <rengolin at gmail.com> wrote:
> On Wed, 11 Sep 2019 at 06:13, Itaru Kitayama via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Hi,
> > I'm still seeing the same ie trying to produce SVE instructions
but
> > resulted in NEONs with Clang as of Sep. 10th.
> > http://lists.llvm.org/pipermail/llvm-dev/2019-March/130788.html
>
> Hi Itaru-san,
>
> IR SVE implementation is ongoing, CC'ing Graham who is leading that
effort.
>
> I'm hoping we can have something working before the next release is
> branched (Dec/Jan), but I don't expect it to be fully featured (inline
> asm, full ACLE, auto-vec in all NEON cases, etc).
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190912/46144c1b/attachment.html>

Hi Itaru,

(and thanks for the replies on this Renato).

We (Arm HPC) initially put up that github branch as an aid to the discussions on
upstream SVE support.  The branch was very old (LLVM-5 based!), and various
aspects of our implementation have changed significantly, following discussions
with the community.  For this reason, we felt that branch was unhelpful at this
point, so have removed it.

The team are working hard on getting SVE codegen support into LLVM, but it’s not
there yet.  For now, this leaves the following options for testing vectorization
with SVE:

  *   Get an up to date GNU compiler, which has SVE vectorization support
  *   Use Arm Compiler for Linux (the new name for Arm Compiler for HPC)

If you’re interested in the latter option, feel free to give me a mail
(will.lovett at arm dot com).  Depending on your use-case, there may be scope
for arranging a license.

Thanks,

Will.


Will Lovett
Technical Product owner
Compilers & Libraries
Arm Allinea Studio

On 11/09/2019, 22:31, "llvm-dev on behalf of Itaru Kitayama via
llvm-dev" <llvm-dev-bounces at lists.llvm.org<mailto:llvm-dev-bounces
at lists.llvm.org> on behalf of llvm-dev at lists.llvm.org<mailto:llvm-dev
at lists.llvm.org>> wrote:

Renato et al.
In the meantime, is there an out of tree branch I mean, other than LLVM trunk so
I can test how much I can SVE vectorize my code with it?

Arm seemed to gave taken down the GitHub branch for sometime.

On Wed, Sep 11, 2019 at 20:41 Renato Golin <rengolin at
gmail.com<mailto:rengolin at gmail.com>> wrote:
On Wed, 11 Sep 2019 at 06:13, Itaru Kitayama via llvm-dev
<llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>>
wrote:
> Hi,
> I'm still seeing the same ie trying to produce SVE instructions but
> resulted in NEONs with Clang as of Sep. 10th.
> http://lists.llvm.org/pipermail/llvm-dev/2019-March/130788.html
Hi Itaru-san,

IR SVE implementation is ongoing, CC'ing Graham who is leading that effort.

I'm hoping we can have something working before the next release is
branched (Dec/Jan), but I don't expect it to be fully featured (inline
asm, full ACLE, auto-vec in all NEON cases, etc).

cheers,
--renato
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190912/d4ef37dc/attachment-0001.html>

Will,
At RIKEN, we have a licence for the Arm Compiler which produces clean SVE
code well, even though that's based upon
7.1.0, but that's a reliable toolchain that enables us for gearing up for
the FUGAKU supercomputer. However, given Clang trunk is already
in 10 series, lots of good features/enhancements are expected there thus,
we're just wondering whether we are honored to
use the current implementation provided by Arm so we can work together.

Good luck to you Arm folks with the on-going work (with the RISC-V
community)! We hope the "Great" merge will happen
sooner than predicted.

Thanks,
Itaru.

On Thu, Sep 12, 2019 at 5:44 PM Will Lovett <Will.Lovett at arm.com>
wrote:
> Hi Itaru,
>
>
>
> (and thanks for the replies on this Renato).
>
>
>
> We (Arm HPC) initially put up that github branch as an aid to the
> discussions on upstream SVE support.  The branch was very old (LLVM-5
> based!), and various aspects of our implementation have changed
> significantly, following discussions with the community.  For this reason,
> we felt that branch was unhelpful at this point, so have removed it.
>
>
>
> The team are working hard on getting SVE codegen support into LLVM, but
> it’s not there yet.  For now, this leaves the following options for testing
> vectorization with SVE:
>
>    - Get an up to date GNU compiler, which has SVE vectorization support
>    - Use Arm Compiler for Linux (the new name for Arm Compiler for HPC)
>
>
>
> If you’re interested in the latter option, feel free to give me a mail
> (will.lovett at arm dot com).  Depending on your use-case, there may be
> scope for arranging a license.
>
>
>
> Thanks,
>
>
>
> Will.
>
>
>
>
>
> *Will Lovett*
>
> Technical Product owner
>
> Compilers & Libraries
> Arm Allinea Studio
>
>
>
> On 11/09/2019, 22:31, "llvm-dev on behalf of Itaru Kitayama via
llvm-dev" <
> llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at
lists.llvm.org>
> wrote:
>
>
>
> Renato et al.
>
> In the meantime, is there an out of tree branch I mean, other than LLVM
> trunk so I can test how much I can SVE vectorize my code with it?
>
>
>
> Arm seemed to gave taken down the GitHub branch for sometime.
>
>
>
> On Wed, Sep 11, 2019 at 20:41 Renato Golin <rengolin at gmail.com>
wrote:
>
> On Wed, 11 Sep 2019 at 06:13, Itaru Kitayama via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Hi,
> > I'm still seeing the same ie trying to produce SVE instructions
but
> > resulted in NEONs with Clang as of Sep. 10th.
> > http://lists.llvm.org/pipermail/llvm-dev/2019-March/130788.html
>
> Hi Itaru-san,
>
> IR SVE implementation is ongoing, CC'ing Graham who is leading that
effort.
>
> I'm hoping we can have something working before the next release is
> branched (Dec/Jan), but I don't expect it to be fully featured (inline
> asm, full ACLE, auto-vec in all NEON cases, etc).
>
> cheers,
> --renato
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190912/5fbb1e2a/attachment.html>

Will,
When you guys announce the SVE codegen support is merged in the trunk,
hopefully in the near future, that means all of the features/functions
that can currently be found in the current release of Arm Compiler for
Linux, correct? We were sitting down this afternoon and wondering about
this a bit thus I am asking.

On Thu, Sep 12, 2019 at 5:44 PM Will Lovett <Will.Lovett at arm.com>
wrote:
> Hi Itaru,
>
>
>
> (and thanks for the replies on this Renato).
>
>
>
> We (Arm HPC) initially put up that github branch as an aid to the
> discussions on upstream SVE support.  The branch was very old (LLVM-5
> based!), and various aspects of our implementation have changed
> significantly, following discussions with the community.  For this reason,
> we felt that branch was unhelpful at this point, so have removed it.
>
>
>
> The team are working hard on getting SVE codegen support into LLVM, but
> it’s not there yet.  For now, this leaves the following options for testing
> vectorization with SVE:
>
>    - Get an up to date GNU compiler, which has SVE vectorization support
>    - Use Arm Compiler for Linux (the new name for Arm Compiler for HPC)
>
>
>
> If you’re interested in the latter option, feel free to give me a mail
> (will.lovett at arm dot com).  Depending on your use-case, there may be
> scope for arranging a license.
>
>
>
> Thanks,
>
>
>
> Will.
>
>
>
>
>
> *Will Lovett*
>
> Technical Product owner
>
> Compilers & Libraries
> Arm Allinea Studio
>
>
>
> On 11/09/2019, 22:31, "llvm-dev on behalf of Itaru Kitayama via
llvm-dev" <
> llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at
lists.llvm.org>
> wrote:
>
>
>
> Renato et al.
>
> In the meantime, is there an out of tree branch I mean, other than LLVM
> trunk so I can test how much I can SVE vectorize my code with it?
>
>
>
> Arm seemed to gave taken down the GitHub branch for sometime.
>
>
>
> On Wed, Sep 11, 2019 at 20:41 Renato Golin <rengolin at gmail.com>
wrote:
>
> On Wed, 11 Sep 2019 at 06:13, Itaru Kitayama via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Hi,
> > I'm still seeing the same ie trying to produce SVE instructions
but
> > resulted in NEONs with Clang as of Sep. 10th.
> > http://lists.llvm.org/pipermail/llvm-dev/2019-March/130788.html
>
> Hi Itaru-san,
>
> IR SVE implementation is ongoing, CC'ing Graham who is leading that
effort.
>
> I'm hoping we can have something working before the next release is
> branched (Dec/Jan), but I don't expect it to be fully featured (inline
> asm, full ACLE, auto-vec in all NEON cases, etc).
>
> cheers,
> --renato
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20190918/c0b14ee8/attachment.html>