Dial in Information

To join the meeting, go to: https://bluejeans.com/8444124406 

Just want to dial in? (http://bluejeans.com/numbers) 

1) +1 408 740 7256 

• +1 888 240 2560 (US Toll Free) 
• +1 408 317 9253 (Alternate Number) 
• +44 203 608 5256 (GB)

2) Enter Meeting ID: 8444124406 

(Try your iPhone or Android phone) 

Live meeting notes are kept in this Google Doc     

Agenda 

• Update on openHPC - Eric Van Hensbergen / Alan Hayward (ARM)
• Update on ARM open source SVE work - Will Lovett (ARM)
• 
  

Minutes

OpenHPC

Release of 1.3 version last week

• Works well on a simple setup

• May not work (not tested) with InfiniBand

• Cavium can help with that

• ARM is using their own compiler to build OpenHPC packages

• May need to have a complete version of the whole system

• Setup a new open build system or use OpenHPC’s own?

• Suse building all packages with their open build system

• Which would probably fragment the ecosystem (PPA?)

• Definite intention to have LLVM

• In addition, libc++, libomp

ARM and Linaro interactions

Compiler upstreaming

• GCC is on a forward branch (not master yet), but usable and being tested by ARM

• People can use it now, but will be officially out not earlier than gcc-8

• Most discussions will be target-independent

• Talk to Maxim to check if we can further validate this (emulator?)

• Binutils is released in 2.28

• LLVM snapshot in GitHub

• Linaro to look again to the MVT patch

• RISC-V guys haven’t came back, so let’s proceed

• SVE docs are public

• This gives us the missing piece to start reviewing patches

• Barring specific complaints, we can start accepting them

• ACLE almost there?

Vector libraries

• Working on Libmvec, parallel-libs

• Initial SVE implementation in the Linux kernel

• Glibc is probably good, not much to do

Fortran

• It’s in ARM’s Clang (PGI’s)

• Worth starting the fight with Flang?

• Do we have support from the community?

• Move to GitHub first, improve and upstream?

• Can ARM validate Fortran internally?

• Talk to Hal Finkel to help

Benchmarks for SVE

• Darren sent a list of SVE-important benchmarks

• We should look at those from a vectorizer point of view

• They’re not used by programs, but they contain common HPC code

Huawei

https://github.com/open-mpi/ompi/issues/2160

Requesting assistance for work on v2.1.0: Fix OOS issues in vader BTL with single-threaded scenarios #2160