similar to: [LLVMdev] why?

Dixi quod… >A checkout of clang r58548 does not build with the prerelease, >seems to require a newer version of llvm-current. However, clang r58565 does not build with llvm r58565 either: llvm[4]: Compiling BasicConstraintManager.cpp for Release-Asserts build mpcxx -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/include -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Anton, please add release_32 also in; clang-tools-extra compiler-rt dragonegg libcxxabi lldb They have release_32 in svn. I don't know they might be released, though. And, could you suppress generating refs/heads/svn-tags and prune them for now? I am sure that orphan branches will stress the llvm.org server to begin git-pack-ing whole tree. ...Takumi 2012/11/15 Anton Korobeynikov

I'm trying to change the Endian of X86 from little to big in the TargetData. I only care about the way in which this effects the LLVM IR, not the actual backend code. I've changed the "e-" to "E-" in X86TargetMachine.cpp (where it sets the DataLayout) with no luck. Are there any other obvious places that I need to change this? The TargetData docs were somewhat helpful

> TL;DR: APT repo switched off due to excessive load / traffic > > Recently we realized that APT repo generates almost 95% of I/O on > llvm.org and more than 40% of network bandwidth alone. During last 2 > weeks the main services on llvm.org (svn, git, bugzilla) had serious > problems with overall connectivity. > > We decided to temporary switch APT repo off to see if this

Is fPIC broken on x86_64 in LLVM 2.6? I looked through the release notes but did not see anything mentioned. When I try: ------------------- > llvm-gcc -Iinclude -emit-llvm -fPIC -O3 -c -o file.opt.bc file.c > llvm-ld -native -Xlinker=-shared -Xlinker=-Wl,-soname,libtest.so -o file.so file.opt.bc ------------------- on an x86 machine it works fine. When I try it on x86_64, the

I have a simple C++ class that looks like this: struct Foo { Thing *first; Blob *second; unsigned long third; }; Then I have a derived C++ class that look like this: struct Bar : Foo { long long fourth; } I generate JIT code to access 'fourth' from a Foo * as follows: BarPtr = CreateBitCast(FooPtr, BarPtrTy); FourthPtr = CreateConstGEP2_32(BarPtr, 0, 3); FourthValue =

Hello, I am building llvm-gcc4.2-2.6 for ARM target.I used the next command line option: >> .../configure --enable-languages=c,c++ --enable-checking --target=arm-eabi >> and then >> make target_alias=arm-eabi >> And then I obtain the following error: In file included from ../../gcc/config/arm/arm.c:59: ../../../libcpp/internal.h: In function ‘ufputs’:

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going

Dear ML, I'm trying to understand how to build a llvm (2.6) cross compiler for arm-elf target using the gcc frontend with newlib. Could you please indicate, if possible steps I should follow? I try to configure and build llvm with ../llvm-2.6/configure --prefix=/usr/local/cross-llvm-gcc-arm-elf-4.2-2.6 --enable-optimized --disable-threads --enable-targets=cbe,cpp,arm and LLVM-GCC frontend

Hello, Attached is a trivial patch to increase the max number of physical registers in LLVM from 1024 to 16384. In our TCE toolset we allow the designer to choose the number of registers in the designed TTA processors freely, and recently while experimenting with using TTA for a GPU design we have bumped into this limit several times. What has made matters a bit worse for us is that we need to

Hi I am running into a legalize dag issue after custom lowering a load. If someone can give me pointers that would be great. I am using llvm 2.6 When custom lowering a load, the following code gets executed. Tmp1 = TLI.LowerOperation(Tmp3, DAG); if (Tmp1.getNode()) { Tmp3 = LegalizeOp(Tmp1); Tmp4 = LegalizeOp(Tmp1.getValue(1)); <----------------- what

Thanx for a prompt reply. I will definitely try llvm 2.8 as per your suggestion. However Step 1 and Step 2 are working for me in case of a simple hello world program on arm processor . Similarly I am able to run a GTK application on arm. However while running wxGTKwidget app it crashes while allocation of memory. As I mentioned earlier, If I explicitly allocate memory using new operation then

Hi! We are running llvm jit x86 on MS Visual Studio 2005. It seems there is a bug in asm code in function X86CompilationCallback in file X86JITInfo.cpp. Current code sets stack pointer to invalid value in instruction "and esp, 16". Depending on current stack pointer value it sometimes overwrites ecx and edx registers with next three lines. We have fixed this problem by changing this

Thanks for your tips. But I'm still getting errors. .../llvm-gcc4.2-2.6.source/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=/home/LLVM/llvm-2.6/ --enable-languages=c,c++  --with-gnu-ld=/home/arm/bin/arm-elf-ld --with-gnu-as=/home/arm/bin/arm-elf-as  --with-cpu=cortex-a8  --target=arm-elf Errors: >> checking for g++ that supports -ffunction-sections

Hi, I'm yet working on the LLVM ExecutionEngine portability (2.6 release version) and I get two different problems depending on the platform. The first problem concerns compilation on MacOs X (10.5.5) with an X86 processor, when trying to compile my own project containing the ExecutionEngine class and the linker class. I get links problem with "_ffi_type_sint16",

Should be there On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Anton, please add release_32 also in; > > clang-tools-extra > compiler-rt > dragonegg > libcxxabi > lldb > > They have release_32 in svn. I don't know they might be released, though. > > And, could you suppress generating refs/heads/svn-tags and prune them

Yes, llvm::InitializeAllTargetMCs(void) does seem to be autogenerated. It is _LLVMInitializeFooTargetMC that I can't find documented anywhere. On Sat, Mar 14, 2015 at 12:05 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > This function is autogenerated. You need also to change top-level > configure / cmake files. > > On Sat, Mar 14, 2015 at 8:38 AM, Daniel

Hello, While trying to create back end in LLVM I have stumbled upon a problem I have trouble to get past, hopefully someone can give me hints on what I am doing wrong. The problem is that the assertion in the file ScheduleDAGList.cpp row 187 is triggered: "Negative latency". How does this happen? As background: My target has one issue unit, therefore my Schedule.td file only

Hello > a) 'llvm-gcc -c -flo -O2' to generate the .bc files. How llvm-gcc was configured & compiled? With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University