similar to: [LLVMdev] [PATCH] .gitignore: add rules for a clean worktree

Hi Dmitri, Dmitri Gribenko wrote: > On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra > <artagnon at gmail.com> wrote: >> Add several .gitignore rules to various directories to ensure a clean >> worktree after a default build. > > Hi, > > These gitignore lists require maintenance. Is is possible to express > the same set of filenames as patterns like

On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Add several .gitignore rules to various directories to ensure a clean > worktree after a default build. Hi, These gitignore lists require maintenance. Is is possible to express the same set of filenames as patterns like '*.inc' in the root gitigrore file, so that adding/removing a new

On Nov 13, 2012, at 8:34 AM, Ramkumar Ramachandra <artagnon at gmail.com> wrote: > Hi Dmitri, > > Dmitri Gribenko wrote: >> On Tue, Nov 13, 2012 at 6:02 PM, Ramkumar Ramachandra >> <artagnon at gmail.com> wrote: >>> Add several .gitignore rules to various directories to ensure a clean >>> worktree after a default build. >> >> Hi,

*I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application programs* (2) tar xzf llvm-2.8.tgz; * // now, the top directory of source tree is /home/qali/llvm-2.8* (3) cd llvm-2.8/projects (4) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

Chandler Carruth wrote: > FWIW, if in-tree builds work for CMake, I consider that a bug and will fix it. How else am I supposed to build LLVM? I ran the toplevel configure and make script. Ram

I have gold from cvs, and llvm-gcc/llvm from svn. My platform is Ubuntu 9.04 x86_64. I've configured llvm-gcc with "--enable-multilib". When compiling the LTO example from http://llvm.org/docs/LinkTimeOptimization.html I have no problems with 64-bit compilation, but get the following with -m32. luked at node:~/tests/lto$ make USE32=1 llvm-gcc -m32 -c -o main.o main.c llvm-gcc

llvm-gcc (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2.9) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. llc --version: Low Level Virtual Machine (http://llvm.org/): llvm version 2.9 Optimized build. Built Mar 5 2012

Dear all, I am trying to build the llvm with cmake and using the following checkouts. LLVM version 3.2svn clang version 3.2 (trunk 158320) (llvm/trunk 158308) cmake runs with default configuration without any problem. cmake ../llvm -- Target triple: i686-pc-linux-gnu -- Native target architecture is X86 -- Threads enabled. -- Building with -fPIC -- Constructing LLVMBuild project information --

---------- Forwarded message ---------- From: Qingan Li <ww345ww at gmail.com> Date: 2011/1/19 Subject: Re: [LLVMdev] About test suits Cont1 To: Eric Christopher <echristo at apple.com> *I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application

One other thing that may or may not illuminate the situation. When I run under gdb (on OS X 10.8.3 this is an ancient version of gdb 6.3.5 - but it works with clang compiled C++ code) I get the following error when I try to list a line in dwarf1.lsp: Dwarf Error: Cannot handle DW_FORM_<unknown> in DWARF reader [in module /Users/meister/Development/cando/src/tests/core/dwarf1.bundle] (gdb)

Hello guys, I'm using llvm 3.3 on windows with mingw (triple: "i386-unknown-mingw32") to compile IR code that my program generates. I do it in two phases: first I emit assembly code and then assemble it. TargetMachine targetMachine = target.createTargetMachine(triple); targetMachine.setAsmVerbosityDefault(true); targetMachine.setFunctionSections(true);

I upgraded my versions of llvm, clang and compiler-rt to the top-of-tree versions from last night (r180162, April 24). I recompiled debug versions of llvm, clang and my code. I then regenerated my test case and the results were the same - I can list lines of dwarf1.lsp in lldb but I can't set break-points or do anything else (what else should I be able to do?). The updated file that

In -help output, -help - Display available options (--help-hidden for more) Both single and double - option markers are accepted, which is good. It would probably be better to refer to options consistently using the single marker in all cases. =linearscan - linear scan register allocator =pbqp - PBQP

Hi Russell, I took care of these points except for > In -version output, > > Low Level Virtual Machine (http://llvm.org/): > llvm version 2.6svn > Optimized build. > Built Feb 14 2010(11:05:20). > > Registered Targets: > alpha - Alpha [experimental] > arm - ARM > bfin - Analog Devices Blackfin [experimental] > c - C

> I was under the impression that in-source-tree builds were an unsupported > configuration. It's certainly strongly discouraged. I'm not fond of the > idea of making it easier, especially when there's a maintenance cost to > doing so. > Strongly discouraged, and yes, this. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Nov 13, 2012 at 12:04 PM, Eric Christopher <echristo at gmail.com> wrote: >> I was under the impression that in-source-tree builds were an unsupported >> configuration. It's certainly strongly discouraged. I'm not fond of the idea >> of making it easier, especially when there's a maintenance cost to doing so. > > Strongly discouraged, and yes,

Hi Kevin, On Tue, May 29, 2012 at 10:22 PM, Kevin Burns <kevinpb at vt.edu> wrote: > > Hello, > > I am currently trying to install vmkit from source. I am running archlinux > i686 with the 3.1.9-2 kernel. This output is from the directions given on > the llvm site. Below is the configureation output along with the make > output. > > > I run ./configure with

On 2011-03-09 02:51, Bill Wendling wrote: > There are LLVM 2.9 RC1 pre-release tarballs source available. You can find them here: > llvm 2.9rc1 test on Dualcore ARM running Ubuntu Natty gunzip llvm-2.9rc1.src.tar.gz tar zxvf llvm-2.9rc1.src.tar cd llvm-2.9-build ../llvm-2.9rc1/configure --enable-shared time make clean ;time make CXXFLAGS=-marm CFLAGS=-marm xranby at

I'm trying to write a script for checking whether the compiler recursed properly. rkotler at mipsswbrd002:~/slave/recurse3be/build$ find . -name "*.o" -exec cmp '{}' ../../recurse2be/build/'{}' \; |& tee foo.txt Is anyone else doing this? There 2 compilers, recurse 2 and recurse3 that in principle should be identical. Obviously if there is date and time

Hello. Excuse me. Why CMakeLists.txt from llvm-3.9.1.src does not contain WebAssembly target? So, it is like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) but not like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ Webassembly X86