search for: power8

What is he most recent version of R known to run reliably in an environment of IBM HPC cluster Power8 systems, Ubuntu 16.04.1 operating environment with gpfs as the cluster file-system? It would seem from 'apt' checking to be R-3.2.3; however, that one is rather old and does not support a sufficient number of R packages that are needed for current university research projects. R-3.5.1 has b...

Bill, On 21 February 2019 at 15:14, Bill Glessner wrote: | What is he most recent version of R known to run reliably in an environment of IBM HPC cluster Power8 systems, Ubuntu 16.04.1 operating environment with gpfs as the cluster file-system? It would seem from 'apt' checking to be R-3.2.3; however, that one is rather old and does not support a sufficient number of R packages that are needed for current university research projects. R-3.5.1 has b...

Hi all, Last year the POWER8 and POWER9 specific improvements (for PowerPC) were completely rewritten, but as of yet no accurate performance tests of these have been performed. I have validated functionality and rough performance checks for these through Travis CI, but the numbers I get through that vary wildly. Recently the...

...un LLDB with the binary just generated > > - Add the breakpoint “b main.cpp:30” > > - Send the command “n”, stepping over to next line. > > Result: The debugger will not stop and will execute the entire binary. > > > Remembering I’m using a little endian Power8 machine. Are there any outstanding patches or workarounds I need to build lldb on Power8? Thanks Sean On Thu, Nov 30, 2017 at 10:09 AM, Leonardo Bianconi < leonardo.bianconi at eldorado.org.br> wrote: > But where is the flat set? Maybe I can debug and check what is going on. > &gt...

Hi, When building LLVM, is it always recommended to do it with the latest official release, currently, it is 9.0.1? I ask because when I tried it with a Debug build, it took an enormous amount of time on POWER8. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200103/f27e32db/attachment.html>

...check for C __attribute__ features Check if compiler supports target attribute on ppc64 Anton Blanchard (5): configure.ac: Remove SPE detection code configure.ac: Add VSX enable/disable configure.ac: Fix FLAC__CPU_PPC on little endian, and add FLAC__CPU_PPC64 Add runtime detection of POWER8 and POWER9 Add VSX optimised versions of autocorrelation loops configure.ac | 53 +- m4/c_attribute.m4 | 18 + src/libFLAC/Makefile.am | 1 + src/libFLAC/cpu.c | 31 + src/libFLAC/include/private/cpu.h | 6 + src/libFLAC/incl...

...mmunity, I'd agree here > but OpenMP 4 offloading is still young. ditto > OpenMP 4 offloading does not yet > have a real user community agreement > yet because the first implementations just > started shipping very recently. Partially strongly disagree - Maybe you meant on Power8? Intel has had their support for OMP4 for quite some time. It may have been buggy and focused on simd directive, but as best I can tell they have worked quite hard to fix bugs and improve it. (Shameless self promotion) We have had some degree of OMP4 offloading for like 1.5 years now.. It's mo...

I have created a JamesOConnor centos wiki userid and I would like to create and be able edit a pair of AltArch wiki pages. https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64le # POWER8 Little Endian https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64 # POWER7 Big Endian These would be linked to from https://wiki.centos.org/SpecialInterestGroup/AltArch similar to the Arm32, AArch64, i386 wiki pages. ppc64le and ppc64 are the POWER rpm arches as defined in redhat-rpm-conf...

Hi Everyone, I'm working on GCC112, which is POWER System S822 (Power8) machine running CentOS 7 machine (https://gcc.gnu.org/wiki/CompileFarm): $ cat /etc/centos-release CentOS Linux release 7.3.1611 (AltArch) I'm trying to determine L1 data cache size. When the following code runs it returns 0. The man pages state -1 is an error, so I think its claimin...

I am pleased to announce the general availability of CentOS Linux 7 (1804) for POWER9 processors (ppc64le - powerpc 64-bit little endian). This release is derived from Red Hat Enterprise Linux 7.5 ALT. Note this release is 99% equivalent to the existing CentOS 7 Linux 7 (1804) for POWER8 processors (ppc64le - powerpc 64-bit little endian). The key difference being that kernel-4.14.0 is used for POWER9 enablement and kernel-3.10.0 is used for POWER8 enablement. You will find the CentOS 7 (1804) Power9 installation images here: http://mirror.centos.org/altarch/7.5.1804/isos/power9/...

...rc/nmath -DHAVE_CONFIG_H -fopenmp -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -c arithmetic.c -o arithmetic.o arithmetic.c:180:26: error: initializer element is not constant 180 | static LDOUBLE q_1_eps = (1 / LDBL_EPSILON); | ^ make[3]: *** [../../Makeconf:124: arithmetic.o...

...-fPIC > -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 > -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong > -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 > -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -c > arithmetic.c -o arithmetic.o > arithmetic.c:180:26: error: initializer element is not constant > 180 | static LDOUBLE q_1_eps = (1 / LDBL_EPSILON); > | ^ >...

Hi all, One of my commit broke the PowerPC builder, so I reverted it. The issue could be reproduced only for big-endian, little-endian ppc64 built ok. How can I fix it? I have no access to any PowerPC box to get to the bottom of issue. All the other tests are ok. Commit: https://github.com/llvm/llvm-project/commit/9c20156de39b377190d7a91783d61877b303fe35, svn revision: 359870. Reproduced

...t; > llvm-dev at lists.llvm.org> wrote: > >> Hi, >> When building LLVM, is it always recommended to do it with the >> latest official release, currently, it is 9.0.1? I ask because when I >> tried >> it with a Debug build, it took an enormous amount of time on POWER8. >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <htt...

...6)count9=count9+1 number=number+1 s=s-1 } power1=count1/number power2=count2/number power3=count3/number power4=count4/number power5=count5/number power6=count6/number power7=count7/number power8=count8/number power9=count9/number print(power1) print(power2) print(power3) print(power4) print(power5) print(power6) print(power7) print(power8) print(power9) I know the programming is not the best but I'm sti...

The `isBranch` flag is already set on the branch instructions. Furthermore, we do use the `isBranch()` query in a few places in the PPC back end, so this does work. Perhaps there's something specific about the lldb usage? Is it somehow possible that the `isBranch()` query is called on the wrong instruction? Would you be able to provide a test case that reproduces the issue? On Thu, Nov 30,

...> >> > OpenMP 4 offloading does not yet >> > have a real user community >> >> agreement >> >> > yet because the first implementations just >> > started shipping very recently. >> >> Partially strongly disagree - Maybe you meant on Power8? >> Intel has had their support for OMP4 for quite some time. It may have >> been buggy and focused on simd directive, but as best I can tell they >> have worked quite hard to fix bugs and improve it. > > I meant across many platforms. Intel had preliminary support for OpenM...

...t;>> >>>> Hi, >>>> When building LLVM, is it always recommended to do it with the >>>> latest official release, currently, it is 9.0.1? I ask because when I >>>> tried >>>> it with a Debug build, it took an enormous amount of time on POWER8. >>>> _______________________________________________ >>>> LLVM Developers mailing list >>>> llvm-dev at lists.llvm.org >>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>>> >>> -------------- next part --------------...

...; charset=utf-8 I am pleased to announce the general availability of CentOS Linux 7 (1804) for POWER9 processors (ppc64le - powerpc 64-bit little endian). This release is derived from Red Hat Enterprise Linux 7.5 ALT. Note this release is 99% equivalent to the existing CentOS 7 Linux 7 (1804) for POWER8 processors (ppc64le - powerpc 64-bit little endian). The key difference being that kernel-4.14.0 is used for POWER9 enablement and kernel-3.10.0 is used for POWER8 enablement. You will find the CentOS 7 (1804) Power9 installation images here: http://mirror.centos.org/altarch/7.5.1804/isos/power9/...

...-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 > > -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong > > -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 > > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 > > -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection > -c > > arithmetic.c -o arithmetic.o > > arithmetic.c:180:26: error: initializer element is not constant > > 180 | static LDOUBLE q_1_eps = (1 / LDBL_EPSILON); > > |...