similar to: [LLVMdev] Impressive amount of warnings

That started happening after someone changed that in compiler-RT, if I'm not mistaken. I'm on holidays with little access to the boards... :( --renato On 18 April 2014 16:54, Tobias Grosser <tobias at grosser.es> wrote: > > > On 18/04/2014 21:29, Renato Golin wrote: >> >> Hi Folks, >> >> We're still seeing an impressive amount of warnings on the

The following failures are consistent on buildbot (and my local box). The Clang one I think it's assuming an Intel box, the other two look like the FileCheck are not good enough. http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4305 Clang :: CodeGen/compound-assign-overflow.c LLVM :: Transforms/LoopStrengthReduce/post-inc-icmpzero.ll LLVM ::

Hello All, I am building llvm-clang cross tool chain for arm target, after successful build for Linux host now I am now building toolchain for *arm target*. However, I am getting below error message which seems to be confusing and not getting any idea how to resolve this issue. *Command :* #CC='clang' CXX='clang++' cmake -G Ninja /home/iiita/crossbuild/llvm

You can compare your configure/build arguments + environment with the build bot: http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4313/steps/configure/logs/stdio I'll check how I built my LLVM on Chromebook tomorrow, but it didn't look too different to yours. --renato On 8 January 2013 19:08, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Tue, Jan 8,

Hi all, In revision 223114 I committed a fix to clang project. It caused fail on clang-native-arm-cortex-a9: http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/23599. According to logs it was a problem with memory allocated by malloc. Reverting the fix in 223120 made the bot green. The changed code does nothing with heap, none of other bots failed, so it looks like a platform

The obvious difference is that you're using --enable-optimized and implicitly --disable-assertions. If you run the tests with make check-all VERBOSE=1 'LIT_ARGS=-v ' > logfile and grep for FAILED in logfile, does what's listed there give any more details? (Quite possible in a Release-Asserts build it might not.) Cheers, Dave -----Original Message----- From: cfe-dev-bounces

Hello All, I am building llvm-clang tool chain for *arm target* by following the steps from http://clang.llvm.org/docs/CrossCompilation.html *However when I tried following cmake command for build tool chain it gives the error message :* #CC='clang' CXX='clang++' cmake -G Ninja /home/iiita/llvm-exp/llvm -DCMAKE_CROSSCOMPILING=True

Hello list, I have some problems using LLVM version 3.8.0 to cross-compile code for ARM Cortex-A9 on x86. I am trying to generate LLVM IR using Clang: clang -S --emit-llvm --target=armv7a-linux-gnueabihf --sysroot=$(ARM_SYSROOT) --gcc-toolchain=$(ARM_GCC_TOOLCHAIN) -c -o translated.ll But somehow clang it is trying to use soft-float and I get the following error: 'gnu/stubs-soft.h' file

Hi renato, 1. The command above is followed by the guide[ HowToCrossCompileLLVM.rst ] and I specify some path(ex. <path-to-host-bin>). 2. The including x86_64 libraries is added because of some missing libraries(ex. "error: Host compiler appears to require libatomic, but cannot find it"). As I have found that the bugs needed to dealt with is some ARM-dependent libraries, I

On Tue, Jan 8, 2013 at 8:31 PM, David Tweed <David.Tweed at arm.com> wrote: > The obvious difference is that you're using --enable-optimized and implicitly --disable-assertions. If you run the tests with > > make check-all VERBOSE=1 'LIT_ARGS=-v ' > logfile > > and grep for FAILED in logfile, does what's listed there give any more details? (Quite possible in

Hi Galina, folks, Does anyone have an idea why the A9 bots are unstable on Clang? They all seem to be the same problem: 1. <eof> parser at end of file Segmentation fault http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/26073/steps/check-all/logs/Clang%3A%3Adead-stores.c

Hi, Hi, I was going through Code of LLVM instruction code generation for ARM. I came across VMLA instruction hazards (Floating point multiply and accumulate). I was comparing assembly code emitted by LLVM and GCC, where i saw that GCC was happily using VMLA instruction for floating point while LLVM never used it, instead it used a pair of VMUL and VADD instruction. I wanted to know if there is

On 26 September 2013 17:52, Stanislav Manilov <stanislav.manilov at gmail.com>wrote: > To answer your question I am testing on a pandaboard currently, which has > an arm cortex-a9 processor, which I think is 64-bit. > Cortex-A9 is still 32-bits, so you'll have all support you need. ;) however it doesn't if I remove the -ffreestanding flag. I need to figure > this out

On 8 January 2013 17:01, Dmitri Gribenko <gribozavr at gmail.com> wrote: > r171853 for this one. Build not finished yet. > http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4312 Thanks!! > LLVM :: Transforms/LoopStrengthReduce/post-inc-icmpzero.ll > > Looks like a better regex can fix this. > I think both of them are just bad FileChecks... This is

Hello everybody, Just a short note that clang build "clang-native-arm-cortex-a9" is broken and the very last successful build was for revision 139932. All newer revisions fail. The builder is available here: http://172.16.0.135:8011/waterfall Thanks Galina

Hi Renato, Thank you very much for the directions, I am going to recommit my fix. What are hardware used in buildbots? Are these common boards like PandaBoard or some thing special? What is RAM installed? Thanks, --Serge 2014-12-11 2:36 GMT+06:00 Renato Golin <renato.golin at linaro.org>: > On 10 December 2014 at 19:06, Serge Pavlov <sepavloff at gmail.com> wrote: > > In

The host c++ standard library is missing <utility>, it appears. On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote: > Please use the correct link : > http://63.145.236.72:8011 > and ignore the previous. > > Also log for broken build is here: > > make[1]: Entering directory >

Hello Renato, It turned out I just didn't do the cross-compilation correctly, and Tim Northover already pointed me to a guide you have written on it ( http://clang.llvm.org/docs/CrossCompilation.html), so I will read that before continuing with my efforts. To answer your question I am testing on a pandaboard currently, which has an arm cortex-a9 processor, which I think is 64-bit. I am much

My understanding is that whether a gcc toolchain defaults to ARM or Thumb is a configuration time decision by whomever builds the toolchain. The linaro arm-linux-gnueabihf toolchain I have defaults to -mthumb and that doesn't vary for -mcpu or any other command line option. I haven't got a gcc to hand that defaults to -marm so that I can test whether -mcpu=cortex-m3 will change that to

I've never tried -mcpu=cortex-xyz but I know -march=armv7 defaults to Thumb OK, I just checked, and -mcpu=cortex-{m3,m4,m7,a7,a9,a15,a53} gives Thumb at -O1, -O1, -Os on the following gcc: arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.3.0-27ubuntu1~18.04) 7.3.0 cortex-m0 fails because it doesn't do hard float. I don't have an eabi compiler around. On Thu, Nov 15, 2018 at 4:14 AM, Tim