similar to: [LLVMdev] Build Failure

On Wed, Jan 2, 2013 at 1:04 PM, <dag at cray.com> wrote: > I'm getting a build failure with -Werror: > > [off-dbg] : [llvm] /ptmp/dag/llvm/official/llvm/lib/IR/Use.cpp: In member function 'llvm::User* llvm::Use::getUser() const': > [off-dbg] : [llvm] /ptmp/dag/llvm/official/llvm/lib/IR/Use.cpp:142:14: error: cast from type 'const llvm::Use*' to type

David Blaikie <dblaikie at gmail.com> writes: > On Wed, Jan 2, 2013 at 1:04 PM, <dag at cray.com> wrote: >> I'm getting a build failure with -Werror: >> >> [off-dbg] : [llvm] /ptmp/dag/llvm/official/llvm/lib/IR/Use.cpp: In member function 'llvm::User* llvm::Use::getUser() const': >> [off-dbg] : [llvm] >>

On Wed, Jan 2, 2013 at 1:31 PM, <dag at cray.com> wrote: > David Blaikie <dblaikie at gmail.com> writes: > >> On Wed, Jan 2, 2013 at 1:04 PM, <dag at cray.com> wrote: >>> I'm getting a build failure with -Werror: >>> >>> [off-dbg] : [llvm] /ptmp/dag/llvm/official/llvm/lib/IR/Use.cpp: In member function 'llvm::User*

On Monday 16 November 2009 14:18, John Criswell wrote: > > Did I miss a message? I am getting tons of compiler errors building > > poolalloc and safecode and am wondering if this patch would fix things. > > What platform are you building on? What types of errors are you > seeing? Edwin's patch will fix warnings for SAFECode on 64-bit platforms. I'm on a 64-bit

I've been unable to bootstrap llvm-gcc-4.0 or -4.2 for x86_64 for some weeks now. The current problem is this: [x86_64-mod-dbg]: ./xgcc -B./ -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/ -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/include -isystem

On Oct 8, 2007, at 12:50 PM, David Greene wrote: > I've been unable to bootstrap llvm-gcc-4.0 or -4.2 for x86_64 > for some weeks now. The current problem is this: > > [x86_64-mod-dbg]: ./xgcc -B./ > -B/install.modified.debug/x86_64-unknown-linux-gnu/x86_64-unknown- > linux-gnu/bin/ > -isystem /install.modified.debug/x86_64-unknown-linux-gnu/x86_64- >

I'm getting this build error with -Werror: [off-opt] : [llvm] cc1plus: warnings being treated as errors [off-opt] : [llvm] /ptmp/dag/llvm/official/llvm/lib/Target/ARM/ARMISelLowering.cpp: In member function 'llvm::MachineBasicBlock* llvm::ARMTargetLowering::EmitAtomicBinary64(llvm::MachineInstr*, llvm::MachineBasicBlock*, unsigned int, unsigned int, bool, bool) const': [off-opt]

On Mon, 8 Oct 2007, Evan Cheng wrote: >> [x86_64-mod-dbg]: /tmp/ccxekXCc.s: Assembler messages: >> [x86_64-mod-dbg]: /tmp/ccxekXCc.s:36: Error: `(%esi,%edi)' is not a >> valid 64 >> bit base/index expression > > Looks like llvm is generating invalid x86-64 assembly. Can you add a - > emit-llvm to the xgcc line and generate a reproducible test case? > Please

On Mon, 8 Oct 2007, Evan Cheng wrote: > I am turning 32-bit add into 32-bit LEA on x86-64 but that's > perfectly legal. Both > leal (%esi,%edi), %eax > leal (%rsi,%rdi), %eax > are legal assembly. It's just the former requires a 67H prefix due to > the 32-bit address size. > > This does point to a performance problem in the 3 address conversion > code (which I

On Wed, 08 Dec 2010 12:09:27 -0600 greened at obbligato.org (David A. Greene) wrote: > Török Edwin <edwintorok at gmail.com> writes: > > > What are we left with then? Only 4.2 and 4.3? > > On SLES 10.1 at least. I think it is highly platform dependent. Also keep in mind that llvm-gcc uses the 4.2 unwinder, so if you are seeing EH failures maybe the EH info generated by

Török Edwin <edwintorok at gmail.com> writes: > What are we left with then? Only 4.2 and 4.3? On SLES 10.1 at least. I think it is highly platform dependent. > I only use 4.4 since a while, and it works fairly well. On what platform? > Are you sure it is not a bug in the regression tests themselves > (strict-aliasing bugs, etc.)? No, I'm not sure. > Which

On Oct 8, 2007, at 4:26 PM, Chris Lattner wrote: > On Mon, 8 Oct 2007, Evan Cheng wrote: >>> [x86_64-mod-dbg]: /tmp/ccxekXCc.s: Assembler messages: >>> [x86_64-mod-dbg]: /tmp/ccxekXCc.s:36: Error: `(%esi,%edi)' is not a >>> valid 64 >>> bit base/index expression >> >> Looks like llvm is generating invalid x86-64 assembly. Can you add

David Greene wrote: > On Monday 16 November 2009 13:04, John Criswell wrote: > >>> [snip] >>> >>> I applied the attached patch to make it compile on my box (Debian >>> x86_64), only to find out that x86_64 is not supported :( >>> This architecture is not supported by the pool allocator! >>> Aborted >>> >> Thanks

Hi David, On Fri, Jul 9, 2010 at 3:25 PM, David Greene <dag at cray.com> wrote: > Now that Bruno is putting in some AVX stuff, it's a good motivator to > move my x86 SIMD reorg work into trunk (and got management to agree to > prioritize it - Thanks Bruno! :) ). > > Attached is the first patch of many to accomplish this.  The overall > goal is to have all x86 SIMD

Now that Bruno is putting in some AVX stuff, it's a good motivator to move my x86 SIMD reorg work into trunk (and got management to agree to prioritize it - Thanks Bruno! :) ). Attached is the first patch of many to accomplish this. The overall goal is to have all x86 SIMD instructions share a set of common patterns so that we can have a more maintainable machine description (e.g. SS, SD,

Török Edwin <edwintorok at gmail.com> writes: >> > Which regression tests are failing with LLVM 2.8 and GCC 4.4.x? >> >> Too many to list. > > Can you give me 2 or 3 examples (that fail with LLVM 2.8 and GCC 4.4 > but work with LLVM 2.8 and GCC 4.3), also I'd like to know how they > fail. > If I have some time I'll check with my 4.4 to see if

David Blaikie <dblaikie at gmail.com> writes: >>> There's little effort to keep the GCC build warning clean, >> >> Why? It seems like a pertty important compiler to support. > > It has some silly warnings (at least in some versions) that we don't > want to workaround/suppress. Arguably we could have the build system > check version information &

I am nuilding that now. CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DBUILD_SHARED_LIBS=ON \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \ -DLLVM_HOST_TRIPLE=x86_64-pc-linux-gnu \ -DLLVM_TARGETS_TO_BUILD="AMDGPU;MSP430;WebAssembly;X86" \

I'm getting the following when building llvm-gcc with an optimized set of LLVM libraries: /ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/xgcc -B/ptmp/dag/build.llvm-gcc-4.2.trunk.official.opt/x86_64-unknown-linux-gnu/./gcc/ -B/cray/iss/compiler/cost/tools/llvm-tools/llvm/install.trunk.official.opt/x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/bin/

Hi, Using master at b0a1c0b72c9c61f8b0a223e08f43498abb64f5e8, I cannot build LLVM. I configured with: CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DBUILD_SHARED_LIBS=OFF \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \