Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] LLVM Build/install error?"
2007 Feb 12
0
[LLVMdev] LLVM Build/install error?
On Mon, 12 Feb 2007, Carsten Reuter wrote:
> I am trying to build and install LLVM onto a current Debian Linux system
> using gcc4 frontend binaries for Red Hat Enterprise Linux4/x86 .
> Using the commands below the Build finishes, ignoring an error that
> comes up again when I try to make install.
> See the messages below. I have no good feeling about the "-i -k" options.
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
Tanya,
Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5)
HIGH LEVEL COMMENTS
* The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't
that be llvm-1.9?
* LLVM was built in Release mode in all cases
* I don't think this is ready for release. In particular the llvm-gcc4
binary
seg faults on FC 5 for most of llvm-test programs.
*
2006 Nov 16
5
[LLVMdev] 1.9 Prerelease Available for Testing
First, thanks for testing this!
> Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5)
>
> HIGH LEVEL COMMENTS
> * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't
> that be llvm-1.9?
We have always labeled the dir just llvm which is fine. If you build llvm
it will know its version 1.9.
> * LLVM was built in Release mode
2007 Mar 29
1
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Yes, you I read that in the docs. Do you have a preferred gcc version
that you would suggest me to work best. Unfortunately, version 3.4.2
that you suggest in your docs fails in compilation too.
Thanks,
Ferad
--
Ferad Zyulkyarov
Barcelona Supercomputing Center
2006 Nov 14
5
[LLVMdev] 1.9 Prerelease Available for Testing
LLVMers,
The LLVM 1.9 Prerelease is available for testing:
http://llvm.org/prereleases/1.9/
If anyone can spare some time, please download the appropriate tarballs
for your platform and test the release (at least with make check). I'd
also appreciate any documentation reviews.
Please note that llvm-gcc3 on x86 may not have a clean dejagnu run. You
should see one XPASS for
2007 Mar 28
5
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Hi,
I tried to compile the GCC front end of LLVM in a 16 CPU SMP machine
with 64bit intel xeon CPUs. I tried with (GCC 4.1.0, 4.1.1, 4.1.2
versions). The LLVM compiles perfectly but when compiling the gcc
front end the compiler crashes with a segmentation fault by reporting
for memory leakages. Probably this is for the GCC's mailing list, but
decided to ask if you know anything more about
2006 Nov 17
2
[LLVMdev] 1.9 Prerelease Available for Testing (TAKE TWO)
Hi Tanya,
Here's my second attempt on Fedora Core 5. The changes this time are:
1. Using GCC 4.0.3 as the compiler
2. Building everything from source (no pre-built binaries used)
BUILD LLVM WITH GCC 4.0.3
* No issues, just the usual warnings.
BUILD LLVM-GCC WITH GCC 4.0.3
* No issues
RUN LLVM-TEST WITH GCC 4.0.3
* The following failures were encountered. Some of them are
2007 Mar 29
1
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Hello, Ferad.
> `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' referenced
> in section `.rodata' of
> /home/ferad/llvm/llvm-obj/Release/lib/libLLVMAnalysis.a(ScalarEvolutionExpander.o):
> defined in discarded section
> `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' of
>
2005 Nov 12
2
[LLVMdev] building LLVM 1.6 on Debian unstable ...
Hi,
Tried to build the 1.6 release on Debian unstable, but ran into link
problems for some utils ...
Copying the messages when building llc, the same error occurs for lli,
llvm-db and some of the examples. Is this a problem with the compiler
version? LLVMSelectionDAG.o itself builds correctly.
make[2]: Entering directory `/home/sameerds/data/llvm-1.6/tools/llc'
llvm[2]: Linking Debug
2006 Apr 14
0
[LLVMdev] Re: standalone llvm
Simon Burton <simon at arrowtheory.com> writes:
>> There are several possibilities here: either add1 is assigned a NULL
>> pointer, or LLVM was unable to use the JIT and generates bytecode
>> instead of native code, or invalid native code was generated
>> (unlikely).
>
> Well, it's not NULL:
>
> (gdb) print add1
> $1 = (int (*)(int)) 0x83e43b8
>
2011 Jul 28
0
[LLVMdev] Build failure for latest source
Attempting to build the latest llvm I get:
llvm[2]: Linking Debug+Asserts executable opt
C:/Utilities/MSYS/build/llvm/Debug+Asserts/lib/libLLVMScalarOpts.a(SimplifyLibCalls.o):C:/Programming/VersionControl/llvm/include/llvm/Instructions.h:388:
undefined reference to
`llvm::GetElementPtrInst::GetElementPtrInst(llvm::Value*, llvm::Value*,
llvm::Twine const&, llvm::Instruction*)'
2014 Mar 11
4
[PATCH] add mips64 support
From: Dejan Latinovic <Dejan.Latinovic at imgtec.com>
---
usr/include/arch/mips64/klibc/archconfig.h | 3 +
usr/include/arch/mips64/klibc/archsetjmp.h | 39 ++++++
usr/include/arch/mips64/machine/asm.h | 76 ++++++++++
usr/include/fcntl.h | 2 +-
usr/include/sys/md.h | 1 +
usr/include/sys/resource.h | 4 +-
2006 Apr 14
2
[LLVMdev] Re: standalone llvm
On Fri, 14 Apr 2006 03:25:39 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
...
> Simon,
>
> With a fresh CVS checkout, I've tried your test case on Windows/VC++
> and it works ok. Too bad that I have not access to a Linux machine
> right now. I'll like to see what's wrong with your test case.
>
> What you get from running the test case under gdb
2006 Apr 14
1
[LLVMdev] Re: standalone llvm
On Fri, 14 Apr 2006 04:05:10 +0200
Oscar Fuentes <oscarfv at telefonica.net> wrote:
>
> This indicates that the JIT is not working and your code is being
> interpreted. I don't know about "llvm-config --libs jit" you are using
> but I would try adding LLVMJIT.o to your link command the same way you
> do with LLVMInterpreter.o
Actually if I _remove_ those other
2005 Nov 12
0
[LLVMdev] building LLVM 1.6 on Debian unstable ...
Sameer D. Sahasrabuddhe wrote:
> Hi,
>
> Tried to build the 1.6 release on Debian unstable, but ran into link
> problems for some utils ...
>
> Copying the messages when building llc, the same error occurs for lli,
> llvm-db and some of the examples. Is this a problem with the compiler
> version? LLVMSelectionDAG.o itself builds correctly.
>
> make[2]: Entering
2005 Nov 12
2
[LLVMdev] building LLVM 1.6 on Debian unstable ...
Marco Matthies wrote:
>> make[2]: Entering directory `/home/sameerds/data/llvm-1.6/tools/llc'
>> llvm[2]: Linking Debug executable llc
>> `.gnu.linkonce.t._ZNK4llvm14TargetLowering12getValueTypeEPKNS_4TypeE'
>> referenced
>> in section `.rodata' of
>> /home/sameerds/data/llvm-1.6/Debug/lib/LLVMSelectionDAG
>> .o: defined in discarded
2018 Mar 02
5
[PATCH 0/5] Various MIPS fixes
Hi,
I noticed that klibc started crashing on 64-bit MIPS and in my quest to fix the
bug I got a bit carried away and fixed a few other things as well. Here are
various miscellaneous MIPS patches, although the first patch is the important
one.
Thanks,
James
*** BLURB HERE ***
James Cowgill (5):
mips64: compile with -mno-abicalls
mips: use -Ttext-segment when linking shared library
2017 Aug 26
2
building release_50 with gcc7.2.0 on MacOS: duplicate symbol llvm::DominatorTreeBase
This is release_50 branch of git,
sha1: f1d5723be3f9456a6b16cdf687847ac2918846de
Using gcc 7.2.0 from homebrew.
$ CC=/usr/local/opt/gcc/bin/x86_64-apple-darwin16.7.0-gcc-7
CXX=/usr/local/opt/gcc/bin/x86_64-apple-darwin16.7.0-g++-7 cmake ..
-DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/Users/andy/local/llvm5
-DCMAKE_PREFIX_PATH=/Users/andy/local/llvm5
$ make VERBOSE=1
[ 92%] Linking CXX
2011 May 06
0
[LLVMdev] Question about linking llvm-mc when porting a new backend
Hello all,
I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping
the related
files from another target and modifying it, I meet a problem when I build
the project. The
error message is as follows:
================================================================
[ 94%] Built target llvm-dis
Linking CXX executable ../../bin/llvm-mc
Undefined symbols:
2010 May 06
2
[LLVMdev] Win32 COFF Support
...
> Thanks, applied in r103150! llvm-mc -filetype=obj probably needs a similar
> patch.
>
>
cool!, I will make that change and submit it too.
> ...
> Yes probably, I don't know what the .def and .scl directives "do" :)
>
>
I think I can figure out the right thing to do here.
> Also, w.r.t. section handling stuff, there is this fixme in the asmprinter: