similar to: [LLVMdev] Follow-up questions after successful upgrade to LLVM 3.0rc4

We were successful in upgrading our JIT project to LLVM 3.0rc4 last week, after initially struggling with the various usage and IR changes from V2.9. But we have some follow-up questions: 1) In spite of building and running our tests cleanly with DEBUG+ASSERTS and RELEASE builds, we consistently see a crash when we use a DEBUG build without ASSERTs. The crash appears whenever we use the

In response to: > Date: Wed, 23 Nov 2011 18:24:16 +0100 > From: Duncan Sands <baldrick at free.fr<mailto:baldrick at free.fr>> > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to > LLVM 3.0rc4 > To: llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> > Hi Kevin, >> Since I don't have llvm-gcc installed, I tried to do the

> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite

陳韋任 <chenwj at iis.sinica.edu.tw> writes: >> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it

On Nov 28, 2011, at 3:44 PM, David A. Greene wrote: > 陳韋任 <chenwj at iis.sinica.edu.tw> writes: > >>> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line

+llvm-dev > On 2016-Feb-09, at 12:54, Harris, Kevin <Kevin.Harris at unisys.com> wrote: > > Duncan, > Kevin Harris here, from Unisys. In our application, generating LLVM IR, we have several instances of code that looks like this: > > . . . > Value* pDS; > . . . > auto argIt = pFunc->arg_begin(); >

Hi, all I want to compile llvm for arm board , running llvm on Devkit8000 cross-compiler : arm-2008q3 (arm-none-linux-gnueabi) below is my configure: ../llvm-2.9/configure --with-llvmgccdir=/home/poki/hybridQ/llvm/llvm-gcc/llvm-gcc-4.2-2.9-i686-linux --enable-optimized --enable-jit --disable-threads

Hello, Are there any issues with Centos 4.4 and asterisk. Thanks in advance Varun

Hi all I want to cross compile llvm for arm architecture on Devkit8000. ARM toolchain: arm-2011.03 LLVM: llvm-2.9 binutils: binutils-2.21 The following is my approach: 1. install binutils- 2.21 put binutils to llvm src directory ./configure --target=arm-linux

The utils/NewNightlyTest.pl script seems to use LLVMGCCDIR in a way that is inconsistent with the top-level configure script. I would like to fix this but I don't want to break everyone's nightly tests. Can someone review the attached patch to make sure I'm not missing something? The NewNightlyTest.pl script checks the LLVMGCCDIR environment variable and uses it for two

Hi, Apparently there are two bugs in tools/llvmc/c: /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item /.../llvm/tools/llvmc/c:28: Error: Expecting a program name /.../llvm/tools/llvmc/c had 2 errors. Terminating. The first error relates to the following line(s): lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \ %llvmgccdir%/lib/gcc/%llvmgccarch% ... the other one to:

On Aug 24, 2007, at 1:52 PM, Holger Schurig wrote: > Is llvmc meant for compilation? > I'm not sure what the status of llvmc is (is anyone working on it?), but I don't believe it was ready for real use or was finished. If you would like to work on it, patches are welcomed! Thanks, Tanya > $ llvmc -c a.c -o a.o > /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output

On Feb 19, 2005, at 20:26, Reid Spencer wrote: > You need to tell configure where the install directory for all of > llvm-gcc is located. Ah ha. That was my problem. I forgot that I ran into this with LLVM 1.4 as well. Basically, I specified: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin instead of: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc Which

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program

I am currently trying to build the CVS version of LLVM, and no matter what I do, ./configure always reports that llvm-gcc cannot be found or is not working. I currently have the LLVM 1.4 llvm-gcc binaries. My path is set correctly: rn-spra1c07:~/llvm/llvm ejones$ which llvm-gcc /Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin/llvm-gcc rn-spra1c07:~/llvm/llvm ejones$ which llvm-g++

Hello... Currently in the process of upgrading Samba v2.0.10 to Samba v3.0.x, while conducting some minimal testing, it turns-out that Samba v3.0.x is performing slower than Samba v2.0.10. Set-ups: A. Samba v3.0.x --> Same PC client is accessing the samba share running on Red Hat 4.5 (64bit, HP DL380) which in turn has an NFS mount coming from another SAN attached Red Hat 4.5 (64bit, HP

On Fri, 20 Aug 2004 08:52:28 -0700 Reid Spencer <reid at x10sys.com> wrote: > Hi Jeff, > > On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > > OK. I've built the front end without any heartaches, but I did > > encountered the following glitches: > > > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to > > try several paths

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

Hi, You need to set the DialPlan parameter to allow the proper number of digits to be collected, for all types of numbers used in your system. I believe that the factory default value would work for long numbers beginning 0011, but your unit was probably previously configured for a different environment or country. Below is an extract from the example in my H.323 firmware; I believe that

Hello, I need to solicit your opinion about something. I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right now the linkers will use this environment variable if it specifies a single directory. It will look in that directory to find libraries when things like -lc or -lcrtend are specified on the command line. Right now, the only known place this is useful to set to is the