similar to: [LLVMdev] LLVM Error

I did a make update. I thought I was running the newest version of compiler-rt. But now I can't even get the project to build. I get the following error: i386-redhat-linux-gnu-clang++: clang/llvm/include/llvm/ADT/SmallVector.h:544: typename llvm::SmallVectorTemplateBase<T, llvm::isPodLike::value>::iterator llvm::SmallVectorImpl<T>::insert(typename

+kcc, llvmdev I think your compiler-rt checkout is out of date, because r188635 is supposed to fix that exact issue. On Mon, Aug 19, 2013 at 9:16 PM, Sharma, Yogesh < Yogesh.Sharma at saabsensis.com> wrote: > Sorry about that. I forgot a d:**** > > ** ** > > ldd (GNU libc) 2.12**** > > Copyright (C) 2010 Free Software Foundation, Inc.**** > > This is free

GNU ld version 2.20.51.0.2-5.36.el6 20100205 Copyright 2009 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) a later version. This program has absolutely no warranty. From: Kostya Serebryany [mailto:kcc at google.com] Sent: Monday, August 19, 2013 5:36 AM To: Sergey Matveev Cc:

This looks like the output of "ld --version". What we need is your glibc version, which is given by "ldd --version". On Mon, Aug 19, 2013 at 8:26 PM, Sharma, Yogesh < Yogesh.Sharma at saabsensis.com> wrote: > GNU ld version 2.20.51.0.2-5.36.el6 20100205**** > > Copyright 2009 Free Software Foundation, Inc.**** > > This program is free software; you may

+llvmdev (llvm-dev does not exist) On Mon, Aug 19, 2013 at 12:58 PM, Sergey Matveev <earthdok at google.com>wrote: > > First, could you please run the test with env.var. > ASAN_OPTIONS=verbosity=1 > > No need for that, actually, since this is a familiar issue. Sharma, could > you please paste the output of "ldd --version" here? > > Sergey > > >

Hello All, I need some help with respect to cross compiling for ARM. While trying to cross compile for the ARM target, I am hitting some errors. I need some help in this. I use the following command to cross compile for ARM Cortex A72 (ARM v8-a), 64 bit architecture: *cmake -v CC='clang' CXX='clang++' -DCMAKE_C_COMPILER=../build_directory_llvm/bin/clang

How do I cross-compile compiler-rt for ARM-Linux with CMake? Given a directory with sub-directories named 'llvm', 'compiler-rt', and 'release' (which is a clang build directory), this build succeeds: $ mkdir -p release-rt $ cd release-rt $ cmake ../llvm -G Ninja \ -DCMAKE_INSTALL_PREFIX=ship \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_ASSERTIONS=ON \

Hi, I am trying to cross compile release-10.x to AArch64 (target=aarch64-linux-gnu), and the directions listed at [1] are not completing the initial cmake step. I'm currently running Manjaro, with the aarch64-linux-gnu package (and associated binutils, headers, and glibc packages). My cmake command is cmake -DCMAKE_CROSSCOMPILING=True -DCMAKE_INSTALL_PREFIX=`realpath install`

But in the first version it's used on the next row: %reg16388<def> = CMPrr %reg16384, %reg16385, %CFR<imp-def,dead>; IntRegs:%reg16388,16384,16385 SKIPCOND 1, *%CFR<imp-use>* Or doesn't that count? Following are patters for cmp and skipcond: def cmpcc : SDNode<"CSISD::CMP", SDTIntBinOp, [SDNPOutFlag]>; let Defs = [CFR] in { def CMPrr :

Hello! I'm working on a new back-end and have hit a bit of a snag. I'm working on getting selectcc working and have followed the MSP430 model of emitting a custom CMP and SELECT_CC node and matching that with a pseudo-instruction that has useCustomEmitter=1. However, my output ends up very wrong, despite the Machine code being initially correct: # Machine code for function func: Function

> What is the exact line you use to configure build tree, and the output you see? cmake ../.. \ -G Ninja \ -DCMAKE_INSTALL_PREFIX=ship \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_ASSERTIONS=ON \ -DLLVM_TARGETS_TO_BUILD=ARM \ -DLLVM_DEFAULT_TARGET_TRIPLE=arm-none-linux-gnueabi \ -DLLVM_TARGET_ARCH=arm-none-linux-gnueabi \ -DLLVM_LIT_ARGS=-v ninja check-all

On Tue, Oct 29, 2013 at 10:55 AM, Greg Fitzgerald <garious at gmail.com> wrote: > > What is the exact line you use to configure build tree, and the output > you see? > > cmake ../.. \ > -G Ninja \ > -DCMAKE_INSTALL_PREFIX=ship \ > -DCMAKE_BUILD_TYPE=Release \ > -DLLVM_ENABLE_ASSERTIONS=ON \ > -DLLVM_TARGETS_TO_BUILD=ARM \ >

Are there any sanitizer lit tests in non-X86 configurations? For example: $ cmake -DLLVM_TARGETS_TO_BUILD=ARM \ -DLLVM_DEFAULT_TARGET_TRIPLE=arm-none-linux-gnueabi \ -DLLVM_TARGET_ARCH=arm-none-linux-gnueabi All ASan tests were removed from the build and all the other sanitizers have tests but they all fail. Should they all be disabled too? Or can we add a REQUIRES tag to get lit to

Hello Per, > The CMPrr instruction is moved down to after the PHI node. My guess is that > the 'dead' in CFR<imp-def,dead> is to blame, but I can't see what I'm doing > differently from MSP430/sparc that makes this not work. Any help GREATLY > appreciated! It seems like no use of CFR after CMP, indeed. How condbranches on your platform look like (patterns, etc.)

> Do I understand correctly that you build Clang that targets ARM on an X86 host? Correct. > If yes, then we should modify compiler-rt CMake rules to check if just-built Clang can target the host system and avoid running any sanitizer tests otherwise. Hmm, depends on the tests, I suppose. If the test runs the executable, then yes it should be disabled (or prefixed with an emulator (i.e.

Yes, I think we should disable sanitizer tests on these platforms. What is the exact line you use to configure build tree, and the output you see? On Fri, Oct 25, 2013 at 2:45 PM, Greg Fitzgerald <garious at gmail.com> wrote: > Are there any sanitizer lit tests in non-X86 configurations? For example: > > $ cmake -DLLVM_TARGETS_TO_BUILD=ARM \ >

I have used S-PLUS, R, MATLAB and SAS for many years, and I am actually quite happy to use any of these four languages. The reason may in part involve my using the various languages for the purposes to which they seem most suited. Hence there are many things for which I would not use SAS or MATLAB, but for which I would greatly prefer to use R instead. On the other hand ( to take one of a

It just occured to me that perhaps what happens is that since the cmp-instruction is initially followed by the pseudo-instruction - which doesn't have Uses = [CFR] - that it's marked dead initially, and never changed back when the SKIPCOND is inserted by the custom emitter? But I feel that this would happen in e.g. MSP430 too then... On Wed, Dec 15, 2010 at 10:14 AM, Anton Korobeynikov

What is the status of i7 architecture support for CentOS-5? Do the latest updates support it? -- This e-mail may contain technical information which is controlled by the United States Government, Department of State, International Traffic & Arms Regulations (ITAR) (22 CFR 120-130) which requires an export license prior to sharing with foreign persons. Lacking such license, ITAR technical

Hello All, I am trying to create a legend for a black-white graph. The package I use is ggplot2. It can add colors to the legend key but not line types. Can you please help? # example from Wickman (2009, ggplot2 - elegant graphics for data analysis, page 109) library(ggplot2) huron <- data.frame(year=1875:1972, level=LakeHuron) ggplot(huron, aes(year)) +