search for: zafena

...r 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 errors http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/i64armLoweringRelatedErrors/ example: root at overo:/home/xerxes/llvm-test/fail/CodeGen/notnativelysupported# llvm-as < 2008-02-04-ExtractSubvector.ll | llc llc: /usr/src/openembedded/overo/tmp/work/armv7a-angstrom-linux-gnueabi/llvm2.6-2.6-r0/llvm...

LLVM ARM v6 backend is in fairly good shape. Even the JIT passes nearly the entire llvm test suite. There are some known missing bits: 1. Exception handling 2. Atomic Not sure: 3. Debugging support (should be trivial to hook up if it's not done) Also the thumb backend is not awesome. Its performance is not great. Evan On Apr 1, 2009, at 6:34 AM, Robert Schuster wrote: > Hi, > the

Hi, the ARM backend lacks some stuff like support for atomic intrinsics. I learned the hard way (crash). Lately I was told that the ARM backend of LLVM is generally in its early stages of development. I would like to know more about this. Which stuff is missing, known to be unstable and the like. Thanks in advance for taking the time. Regards Robert -------------- next part -------------- A

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...

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...

...beagleboard, it took about 4 hours to build without the tests which is a bit too slow. We will need to find a way to make ARM builds faster. Thanks Galina On Fri, Apr 8, 2011 at 5:46 AM, Renato Golin <renato.golin at arm.com> wrote: > 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...

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:

Duncan Sands skrev: > 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: 0x614e...

...gh QEMU) but getting the error as mentioned in previous mail. VM is running ARM926 which according to ARM architecture, has vfp support. Do some changes need to me made in LLVM distribution to make it run on ARM platforms Thanks --Kapil On Fri, Sep 25, 2009 at 5:16 AM, Xerxes Rånby <xerxes at zafena.se> wrote: > 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/llv...

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

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

Hi Jin-Gu Kang! It are possible that the problem you are experiencing have already been solved in the current llvm 2.6 release tree and the current svn trunk. So try using llc from llvm 2.6 release branch or llvm pre2.7 svn trunk! It would be helpful if you could open a bugreport for this issue and attach the problematic od.bc since we need a testcase from the bitcode that exposes the bug inorder

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

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:

...mgcc-4.2.1... so should i need to compile the kernel and rootfs with armgcc-4.3.3? If i want to use arm-toolchain-4.2.1 , what should i do for clearing the instruction cache call in lib/System/Memory.cpp? Thanks and Regards, Prasanth J On Mon, Nov 16, 2009 at 4:12 PM, Xerxes Rånby <xerxes at zafena.se> wrote: > > 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 >...

...rror 2 make[1]: Leaving directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm-obj/tools' make: *** [all] Error 1 can anyone please tell me why am i getting this error and how can i resolve this? Thanks and Regards, Prasanth J On Mon, Nov 9, 2009 at 5:20 PM, Xerxes Rånby <xerxes at zafena.se> wrote: > 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 --ta...

...]: *** [Analysis/.makeall] Error 2 make[1]: Leaving directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib' make: *** [all] Error 1 please let me know how should i resolve this error... Thanks and Regards, Prasanth J On Fri, Nov 13, 2009 at 7:39 PM, Xerxes Rånby <xerxes at zafena.se> wrote: > Prasanth J wrote: > > > > Hi all, > > with reference to the reply below, I downloaded toolchain from > > codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... > > when i compile llvm+clang with this toolchain i am getting the > &...

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 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 \ --disable-threads --enable-targets=cbe,cpp,arm using this