similar to: running on a ppc

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

I try to build a cross powerpc compiler, but llvm-gcc fails. Eric Christopher wrote: > Looks like you don't have an assembler for your target installed that > llvm-gcc can find. I have binutils installed for powerpc and verified they are working with a simple hello world program. $ powerpc-750-linux-gnu-as --version GNU assembler 2.16.1 However, the xgcc build during the seems to

Hi, When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got the following error : -------------------------------Compilation error listing if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi make GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc -B/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/

> I try to build a cross powerpc compiler, but llvm-gcc fails on > crtstuff.c / crtbegin.o In the archives I found a thread where more or less the same problem is discussed: http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-January/037327.html Can I conclude from this that indeed llvm-gcc for powerpc-linux is broken? Is anyone maintaining llvm-gcc for powerpc-linux or is it abandoned?

Duncan, et al., I am interested in getting dragonegg to work on PowerPC. Obviously the stuff in src/x86 needs to be replaced/replicated for PowerPC, but if you have a few minutes, can you provide your thoughts on what has to be changed between x86 and PPC. Thanks in advance, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory

Hi Ulrich, and any other llvm PowerPC/JIT users, It looks like the Numba maintainers have run in to an issue with RuntimeDyldELF's PowerPC support (See https://github.com/numba/numba/issues/2451#issuecomment-377739948 and later comments) Due to a recent change to weak symbol handling, we now always resolve to the first copy of a function that is emitted (discarding redundant weak/odr

> Okay, I took a closer look at your output. > > I was correct in that gccas is attempting to assemble a native PPC > assembly language file. However, this appears to be happening because > the assembly file is generated by the GCC Makefiles for libgcc2 (in > llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). > > The first thing I would try is Marco's suggestion: add

Full_Name: Luca Barbato Version: 2.3.1 OS: Gentoo Linux/PPC Submission from: (NULL) (151.44.163.144) system informations Portage 2.1 (default-linux/ppc/ppc32/2006.0/G4, gcc-4.1.1, glibc-2.4-r3, 2.6.17-rc5 ppc) ================================================================= System uname: 2.6.17-rc5 ppc 7447A, altivec supported Gentoo Base System version 1.12.1 distcc 2.18.3

Hi, Maarten > Can I conclude from this that indeed llvm-gcc for powerpc-linux is broken? > Is anyone maintaining llvm-gcc for powerpc-linux or is it abandoned? IIRC, llvm-gcc can be built successfully on a Linux/PowerPC machine. Here was my configuration, $ ../llvm-gcc-4.2-2.8.source/configure --prefix=/path/to/install --program-prefix=llvm- --enable-llvm=/path/to/install

Hi Hal, > I am interested in getting dragonegg to work on PowerPC. Obviously the > stuff in src/x86 needs to be replaced/replicated for PowerPC, but if you > have a few minutes, can you provide your thoughts on what has to be > changed between x86 and PPC. you should probably start by doing this: copy gcc/config/rs6000/llvm-rs6000.cpp to (in the dragonegg source) src/ppc/Target.cpp.

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v8 -> v9: mv qspinlocm config entry to

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v8 -> v9: mv qspinlocm config entry to

Compilation was ok with klibc-1.5.10 on linux-2.6.25. Distrib does not matter as it is inside a chroot a la LSF With the upgrade to linux-2.6.27 it broke on 1.5.10 (I try too the last 1.5.14) with make[1]: Entering directory `/usr/src/klibc-1.5.14' GEN klcc/klibc.config GEN klcc/klcc HOSTCC scripts/basic/fixdep KLIBCCC usr/klibc/__static_init.o KLIBCCC usr/klibc/vsnprintf.o

On Oct 5, 2011, at 8:22 AM, Hal Finkel wrote: > I've been working on adding support for the PPC 440/450 "embedded" cores > to the PowerPC backend. These are used on IBM's Blue Gene L and P > supercomputers, but are also used in other environments (like on the > Xilinx Virtex-5). Here is my first patch. I'm new to LLVM, and so I > apologize if this is the wrong

I've been working on adding support for the PPC 440/450 "embedded" cores to the PowerPC backend. These are used on IBM's Blue Gene L and P supercomputers, but are also used in other environments (like on the Xilinx Virtex-5). Here is my first patch. I'm new to LLVM, and so I apologize if this is the wrong way to do this [the online docs seem to imply that a patch should be

Hi All, I try to build a cross-compiler that compiles for powerpc but runs on my pentium. As a base I used the arm cross-compiler script but changed: CROSS_HOST="x86_64-unknown-linux-gnu" CROSS_TARGET="powerpc-linux" CROSS_MARCH="750" LLVM is building ok, but the second step: building llvm-gcc fails with a rather strange error which I appended to the end of this

Hi, I am wondering why we dont support PPC32 LE? Here is the output of llvm-mc --version, in which only PPC32, PPC64 & PPC64LE are supported. $ llvm-mc --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build with assertions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64

This is not, strictly speaking, an LLVM issue, but it is an implementation matter that a compiler using LLVM needs to handle. I've got resolutions for other platforms, but I'm not seeing how to get this done for PowerPC, and I'ld appreciate suggestions or pointers. For BitC procedures that require an environment pointer, our general approach has been to construct a heap-allocated

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v7 -> v8: add one patch to drop a function call

Hi All, this is the fairlock patchset. You can apply them and build successfully. patches are based on linux-next qspinlock can avoid waiter starved issue. It has about the same speed in single-thread and it can be much faster in high contention situations especially when the spinlock is embedded within the data structure to be protected. v7 -> v8: add one patch to drop a function call