search for: power7

Hi Everyone, I'm having trouble figuring out a compile failure on ppc64le. The failure is at https://travis-ci.org/noloader/cryptopp-autotools/jobs/602187190 . The message is: /bin/bash ./libtool --tag=CXX --mode=compile clang++ -DHAVE_CONFIG_H -I. -DCRYPTOPP_DISABLE_POWER8 -pipe -mcpu=power7 -mvsx -maltivec -g -O2 -MT libppc_power7_la-ppc_power7.lo -MD -MP -MF .deps/libppc_power7_la-ppc_power7.Tpo -c -o libppc_power7_la-ppc_power7.lo `test -f 'ppc_power7.cpp' || echo './'`ppc_power7.cpp ppc_power7.cpp:71:21: error: use of undeclared identifier 'vec_xl'...

Hello Centos fellows, I liked to run Centos on my IBM Power7 machine and therefore I used to download the images form: <http://isoredirect.centos.org/altarch/7/isos/ppc64/> http://isoredirect.centos.org/altarch/7/isos/ppc64/ But not it seems that this link is not working: The requested branch/release/arch/filename does not seem to be valid, pl...

On 31/12/2018 19:00, christian.sonnemans at xs4all.nl wrote: > Hello Centos fellows, > > I liked to run Centos on my IBM Power7 machine and therefore I used to > download the images form: > > <http://isoredirect.centos.org/altarch/7/isos/ppc64/> > http://isoredirect.centos.org/altarch/7/isos/ppc64/ > > But not it seems that this link is not working: > The requested branch/release/arch/filename...

On 12/31/18 10:00 AM, christian.sonnemans at xs4all.nl wrote: > Is Centos 7 no longer supporter for IBM Power 7 machines witch uses centos > Big Endian 64 bits ? I'm not sure, but ppc64 is mentioned in "special notes" in the most recent release announcement for alt arch: https://lists.centos.org/pipermail/centos-announce/2018-December/023083.html

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, is there anybody here who has access to such a machine and could test errrr... 'some software' there? Please mail me privately. Thanks & best, Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFNQYqAfg746kcGBOwRArE2AJ4+qtS3i0V6a0Y6WocbpGZfne7Q/wCgsphj 1JcOBKH2RuleIQ3X80XFfT4= =AEdz -----END PGP

On Thu, Oct 24, 2019 at 2:22 PM Jinsong Ji <jji at us.ibm.com> wrote: > Looks like to me that your clang is too old. > > clang version 3.8.0-2ubuntu4 (tags/RELEASE_380/final) > > clang 3.8.0 was released on 08 Mar 2016. > > While vec_xl was added in https://reviews.llvm.org/rL286455 onNov 11 > 2016, which is around half an year later then 3.8.0. > > Can you

...This can be used with the opt program, and also via Clang by passing: -mllvm -use-cfl-aa. For the purpose of testing with those targets that make use of aliasing analysis during code generation, there is also a corresponding -use-cfl-aa-in-codegen option. Running the test suite on one of our IBM POWER7 systems (comparing -O3 -mcpu=native to -O3 -mcpu=native -mllvm -use-cfl-aa -mllvm -use-cfl-aa-in-codegen [testing without use in code generation were essentially the same]), I see no significant compile-time changes, and the following performance results: speedup: MultiSource/Benchmarks/mafft...

Hey Galina, Will; I've been working to revive the PPC64 build bots, and succeeded, but not for the right reasons. There were still bootstrap assertion failures and other pretty blatant errors. Then we figured out why: the Clang bootstrapping build bots for Power7 are not actually running any of the Clang tests! Could one of you tweak this build bot's configuration to match the other bootstrap bot configurations that run both LLVM and Clang tests? Is there a a Clang PPC64 build bot that *doesn't* self-host so we can get faster turn around? I think...

...So we can see almost all got worse performance. > > The command line option I'm using is "-O3 -std=gnu89 -ffast-math -fslp-vectorize -fvectorize -mcpu=cortex-a57 -mllvm -use-cfl-aa -mllvm -use-cfl-aa-in-codegen" > > I didn't try compile-time, and I think your test on POWER7 native build should already meant something for other hosts. Also I don't have a good benchmark suit for compile time testing. My past experiences showed both llvm-test-suite (single/multiple) and spec benchmark are not good benchmarks for compile time testing. > > Thanks, > -Jiangnin...

Hi all, I have been experiencing the failure of the address sanitizer regression tests for a PPC64 target (Power7 machine). My understanding is that most of the failures are related with the fact the stack is not being dumped. I tried to understand what might be wrong and started by looking into the null_deref.cc test as it hangs during the test run. I observe that after the detection of the faulty memory ac...

...performance. >> >> The command line option I'm using is "-O3 -std=gnu89 -ffast-math >> -fslp-vectorize -fvectorize -mcpu=cortex-a57 -mllvm -use-cfl-aa >> -mllvm -use-cfl-aa-in-codegen" >> >> I didn't try compile-time, and I think your test on POWER7 native >> build should already meant something for other hosts. Also I don't >> have a good benchmark suit for compile time testing. My past >> experiences showed both llvm-test-suite (single/multiple) and spec >> benchmark are not good benchmarks for compile time testin...

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-config: https://git.centos.org/blob/rpms!redhat-rpm-config.git/598fb18c10fe9b1984fba62...

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;chandlerc at gmail.com> wrote: > I've been working to revive the PPC64 build bots, and succeeded, but > not for the right reasons. There were still bootstrap assertion > failures and other pretty blatant errors. Then we figured out why: > the Clang bootstrapping build bots for Power7 are not actually > running any of the Clang tests! > > Could one of you tweak this build bot's configuration to match the > other bootstrap bot configurations that run both LLVM and Clang tests? Maybe I'm confused somehow, but I thought this one: http://lab.llvm.org:8011/builde...

...see almost all got worse performance. > > The command line option I'm using is "-O3 -std=gnu89 -ffast-math > -fslp-vectorize -fvectorize -mcpu=cortex-a57 -mllvm -use-cfl-aa > -mllvm -use-cfl-aa-in-codegen" > > I didn't try compile-time, and I think your test on POWER7 native > build should already meant something for other hosts. Also I don't > have a good benchmark suit for compile time testing. My past > experiences showed both llvm-test-suite (single/multiple) and spec > benchmark are not good benchmarks for compile time testing. > > Th...

...unt8+1 if(d9>1.96)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...

...30 in __msan::MsanThread::ThreadStart() /home/seurer/llvm/llvm-test/projects/compiler-rt/lib/msan/msan_thread.cc:77 #2 0x10d5c07c0 in MsanThreadStartFunc(void*) /home/seurer/llvm/llvm-test/projects/compiler-rt/lib/msan/msan_interceptors.cc:1080 #3 0x7fff819dbf54 in start_thread (/lib64/power7/libpthread.so.0+0xbf54) #4 0x7fff8172657c in __GI___clone (/lib64/power7/libc.so.6+0x16657c) SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/seurer/llvm/llvm-test/projects/compiler-rt/test/msan/dtls_test.c:22:7 in Thread1 Exiting If I run it on an older system with glic 2.17 in...

...ch/powerpc/kvm/Kconfig > @@ -79,6 +79,7 @@ config KVM_BOOK3S_64_HV > select KVM_BOOK3S_HV_POSSIBLE > select MMU_NOTIFIER > select CMA > + select KVM_CROSS_ENDIAN_GUESTS > ---help--- > Support running unmodified book3s_64 guest kernels in > virtual machines on POWER7 and PPC970 processors that have > diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig > index c18f9e6..0c4ce47 100644 > --- a/drivers/net/Kconfig > +++ b/drivers/net/Kconfig > @@ -261,6 +261,7 @@ config TUN > config TUN_VNET_CROSS_LE > bool "Support for cross-endian...

...ch/powerpc/kvm/Kconfig > @@ -79,6 +79,7 @@ config KVM_BOOK3S_64_HV > select KVM_BOOK3S_HV_POSSIBLE > select MMU_NOTIFIER > select CMA > + select KVM_CROSS_ENDIAN_GUESTS > ---help--- > Support running unmodified book3s_64 guest kernels in > virtual machines on POWER7 and PPC970 processors that have > diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig > index c18f9e6..0c4ce47 100644 > --- a/drivers/net/Kconfig > +++ b/drivers/net/Kconfig > @@ -261,6 +261,7 @@ config TUN > config TUN_VNET_CROSS_LE > bool "Support for cross-endian...

Hello, I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7 p770) installation. yum update stops with Error: Multilib version problems found. [..] Protected multilib versions: systemd-libs-219-42.el7.ppc != systemd-libs-219-42.el7_4.1.ppc64 When I scroll back through the transaction check I see various package dependencies for *.ppc instead of *.ppc64. Fi...