similar to: [LLVMdev] cmake configured buildbot

On Tue, Jun 30, 2009 at 1:12 PM, Douglas Gregor<dgregor at apple.com> wrote: > > On Jun 30, 2009, at 6:52 AM, Xerxes Rånby wrote: > >> Greetings >> >> Im interested to setup an automated buildbod that can test the cmake >> buildsysten. >> I use cmake for ARM cross compilation so I would be interested if >> someone are running a cmake bot and if

On 07/23/2009 10:39 AM, Daniel Dunbar wrote: > On Tue, Jun 30, 2009 at 1:12 PM, Douglas Gregor<dgregor at apple.com> wrote: >> On Jun 30, 2009, at 6:52 AM, Xerxes Rånby wrote: >> >>> Greetings >>> >>> Im interested to setup an automated buildbod that can test the cmake >>> buildsysten. >>> I use cmake for ARM cross compilation so I

On Jun 30, 2009, at 6:52 AM, Xerxes Rånby wrote: > Greetings > > Im interested to setup an automated buildbod that can test the cmake > buildsysten. > I use cmake for ARM cross compilation so I would be interested if > someone are running a cmake bot and if its build logs be observed > online? I don't know of anyone doing this now. > If not, are there an easy way

Hi Tanya, Bill, Anton and Martin. I have recently set-up and installed a ARM buildbot that have currently been building since August 21. You can follow its progress here http://google1.osuosl.org:8011/builders/llvm-arm-linux I have also started to investigate the test failures and writing bugreports. Currently about all test failures except are related to the ExecutionEngine JIT and i am doing

Hello Evan and Robert I have been investigating the unexpected test failures from the ARM nightly builders in order to get a better picture why the ARM backend don't pass the whole testsuite: I have run the failing tests manually on my arm board and can now categorize most of the thirteen unexpected CodeGen failures in four categories: 1. llvm don't lower MVT::i64 properly on arm

On 8 April 2011 11:21, Xerxes Rånby <xerxes at zafena.se> wrote: > Hope this will help fix the regressions Hi Xerxes, I see you're the owner of that board, thanks for the detailed description of the tests. By what you say, I think that the board itself is serving its purpose, and 2.9 only got that regression because it wasn't fixed it in time. My intention was to know what can

llvm/lib/System/Atomic.cpp contains the call to __sync_val_compare_and_swap that lowers to the missing __sync_val_compare_and_swap_4 GCC intrinsic. The same file contains several other __sync_* calls and all these has to be implemented if we want to be able to compile llvm on linux/ARM with GCC versions below < 4.4 xerxes at labbserver:~/llvm$ grep _sync lib/*/* lib/System/Atomic.cpp:

Why is his configure not catching this? It tests for the linkability of these functions on the target arch, and should be detecting their absence if that is actually the case. --Owen On Jul 1, 2009, at 12:50 AM, Xerxes Rånby wrote: > llvm/lib/System/Atomic.cpp contains the call to > __sync_val_compare_and_swap that lowers to the missing > __sync_val_compare_and_swap_4 GCC

On Aug 27, 2009, at 2:20 PM, Xerxes Rånby wrote: > I have recently set-up and installed a ARM buildbot Wonderful. It would be helpful to write up a bug report for the bits that don't work, and then to XFAIL them, so that the bot turns green. People watch mainly for the green to red transitions, and having it forever be red (orange) isn't as useful.

Hi Renato, >I was recently investigating the build bot infrastructure and noticed >that the arm-linux target is failing for quite a long time. I believe >that it means ARM code is not executed all that often in LLVM tests, >is that correct? >We were wondering what kind of support we could give to make sure ARM >code is correct and don't regress, specially before releases (I

On 2011-04-08 08:58, Duncan Sands wrote: > Hi Renato, > >> I was recently investigating the build bot infrastructure and noticed >> that the arm-linux target is failing for quite a long time. I believe >> that it means ARM code is not executed all that often in LLVM tests, >> is that correct? Hi i will summarise the last sucessfull builds by the ARM builder:

Hi Kapil! LLVM both builds and runs fine on ARM Linux. I am running a public buildbot for the llvm project that are compiling and testing llvm on arm-linux daily and this machine are running Ubuntu Jaunty. http://google1.osuosl.org:8011/builders/llvm-arm-linux I have successfully compiled LLVM on ARM using GCC 4.3.3 on a Ubuntu Jaunty system and GCC 4.4 on a Ubuntu Karmic system. Do you use

I have tested compiling vmkit using gcc3.4 and gcc4.4 Some vmkit files required that I added some explicit typecasts and #includes in order to compile. I have attached my changes against the vmkit svn trunk rev 69439 Using this patch both versions of gcc managed to compiled vmkit on my machine. Cheers Xerxes -------------- next part -------------- An embedded and charset-unspecified text was

ons 2011-08-31 klockan 10:51 +0200 skrev Ralf Karrenberg: > Hi Matt, hi Bruno, > > I am still struggling to use AVX via MCJIT on TOT... did you succeed yet? > > I seem to be unable to even get lli to run some code with the > "use-mcjit" flag. > I attached a test case that works fine for "lli y.bc" but exits with an > error for "lli -use-mcjit

On Mar 15, 2011, at 4:45 AM, Xerxes Rånby wrote: > On 2011-03-14 18:14, Anton Korobeynikov wrote: >> Hello Xerxes, >> >>> llvm 2.9rc1 test on Dualcore ARM running Ubuntu Natty >> What is the gcc used for the compilation? Can you try to do the -O0 >> build and see whether this changed the stuff? >> > > xranby at panda:/media/dh0/llvm-2.9-build-O0$

Frits van Bommel skrev: > Benjamin Kramer wrote: > >> At the moment llvm-config outputs "2.6svn" if llvm is build from trunk >> >> $ llvm-config --version >> 2.6svn >> >> Some external projects (built out-of-tree) need to know which revision >> of llvm is installed. LDC currently asks llvm-config --src-root for the >> source

Prasanth J wrote: > Hi, > > As you said i downloaded arm toolchain from codesourcery(2009q3 with > gcc 4.4.1 version).. if i use this toolchain i am getting the > following error.. > > make[2]: Entering directory > `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis' > llvm[2]: Compiling LoopPass.cpp for Release build > if arm-none-linux-gnueabi-g++

Prasanth J skrev: > Hi, > > i am a newbie to llvm architecture. i have been trying to port llvm on > ARM target. i am using the following configuration for cross compiling > llvm. > > ../llvm/configure --host=arm-linux --target=arm-linux > --build=i686-linux --prefix=/opt/llvm-arm/ --enable-optimized > --disable-debug \ > --disable-expensive-checks --disable-doxygen

Hi, I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. but when i tried to run it on target it shows GCC 4.3.0 version not found. So i copied the runtime libraries (libc.so and libgcc_s.so) from the toolchain to the target and exported its path in LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its crashing with Segmentation fault. What could be the problem

Hi Xerxes, > 4. softfloat related errors > http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ > example: > > root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc > SoftenFloatResult #0: 0x614e00: f32 = undef > llc: