search for: armv5

...now > free of whatever bugs caused these things to fail (ie: it's not just that > these stopped failing on this hardware but in all environments the xfail is > for) then they should just be un-xfailed. > Sorry, I got confused... starting over... Some tests fail on ARMv7, others on ARMv5, and ExecutionEngine is old enough (and never worked properly on ARM) for me to care much for it. My question, and I think I have answered, is if it was possible to specify sub-arch, and it is if it's in the triple (right?), so "XFAIL: armv5" should do the trick if "armv5" i...

On Feb 26, 2013 2:13 AM, "Renato Golin" <renato.golin at linaro.org> wrote: > > Hi folks, > > The llvm-arm-linux buildbot, although old, is up and running and the only failures I can see were XFAIL, but still being run on ARM: > > http://lab.llvm.org:8011/builders/llvm-arm-linux/builds/2158 > > Any ideas why they're still being run on that buildbot?

Hi folks, The llvm-arm-linux buildbot, although old, is up and running and the only failures I can see were XFAIL, but still being run on ARM: http://lab.llvm.org:8011/builders/llvm-arm-linux/builds/2158 Any ideas why they're still being run on that buildbot? If we can clear those, we can get it passing again. cheers, --renato -------------- next part -------------- An HTML attachment was

...; /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll | /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./FileCheck /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll -check-prefix ARGUMENT /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./llc -mtriple armv5 -O0 < /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll | /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./FileCheck /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll -check-prefix ARGUMENT /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./llc -...

On Wed, Mar 20, 2013 at 6:42 AM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: > Current llvm svn fails make check when built for only x86... Ah, right, need to put that behind a "requires"... hrm. (or I could just drop it & let the machines that are armv5 native catch this) > > [100%] Running the LLVM regression tests > FAIL: LLVM :: DebugInfo/inlined-vars.ll (3994 of 7466) > ******************** TEST 'LLVM :: DebugInfo/inlined-vars.ll' FAILED ******************** > Script: > -- > /sw/src/fink.build/llvm33-3.3-0/llvm-3....

...On Wed, Mar 20, 2013 at 6:42 AM, Jack Howarth <howarth at bromo.med.uc.edu> wrote: >> Current llvm svn fails make check when built for only x86... > > Ah, right, need to put that behind a "requires"... hrm. (or I could > just drop it & let the machines that are armv5 native catch this) > >> >> [100%] Running the LLVM regression tests >> FAIL: LLVM :: DebugInfo/inlined-vars.ll (3994 of 7466) >> ******************** TEST 'LLVM :: DebugInfo/inlined-vars.ll' FAILED ******************** >> Script: >> -- >> /sw/src...

...at the instruction set does; unfortunately that set > doesn't include me... > Hi David, I'll move all remote tests to a dir and mark them unsupported for now. What about the ExecutionEngine unittest below? Can you fix it? Or disable it on ARM? http://lab.llvm.org:8011/builders/llvm-armv5-linux/builds/298/steps/test-llvm/logs/LLVM-Unit%20%3A%3A%20ExecutionEngine__MCJIT____wd__buildbot__llvm-armv5-linux__llvm__unittests__ExecutionEngine__MCJIT__Debug%2BAsserts__MCJITTests__MCJITTest.return_global cheers, --renato -------------- next part -------------- An HTML attachment was scrubbe...

...the clang > patch for cross-compilation is reviewed and applied. Hi Renato, I dont want to generate Thumb code, actually i missed in my previous email that "rrx r0,r0" is both ARM and thumb-2 instruction, but only defined in ARMv7. llvm produces "rrx r0,r0" mnemonics for ARMv5 targets, however ARM Architecture Reference Manual for ARMv5 doesn't know about that mnemonics. There is equivalent mnemonics on ARMv5: "mov r0,r0, rrx" both "rrx r0,r0" and "mov r0, r0, rrx" result in same opcode: 0xe1a00060. Problem is that in case when old bin...

> I'll move all remote tests to a dir and mark them unsupported for now. What > about the ExecutionEngine unittest below? Can you fix it? Or disable it on > ARM? If I read your summary correctly it's only failing armv5. I wouldn't want to stop testing it on everything else because of an ancient box like that. Cheers. Tim

...# /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c clang version 3.0 (http://llvm.org/git/clang.git 98138cdfdee05c0afbab2b209ce8cfe4a52474e1) Target: arm-unknown-freebsd Thread model: posix "/opt/llvm/bin/clang" -cc1 -triple armv5e-unknown-freebsd -S -disable-free -main-file-name rrx.c -mrelocation-model static -mdisable-fp-elim -mconstructor-aliases -target-abi apcs-gnu -target-cpu arm926ej-s -msoft-float -mfloat-abi soft -target-feature +soft-float -target-feature +soft-float-abi -target-feature -neon -target-linker-versio...

Hi Xerxes, It seems that your bot is broken for a while now, but doesn't look like a genuine LLVM error, maybe it just need some cleaning / re-configuring the build system? cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130922/165ebcf7/attachment.html>

...as source > register. > In 2007 a patch was discussed at the mailing list, however my compiler still is > producing this result. Does anyone know if this patch is actually applied? > > * I use the following arguments: > llvm-gcc -mfpu=vfp -mlittle-endian -mfloat-abi=softfp -march=armv5 -S > -O3 foo.c -S -o foo.s > * Attached to this document foo.c and the resulting foo.s. Please, take note of > the illegal instruction mul r0, r0, r2 at line 18. > * The patch is discussed at: > http://www.mail-archive.com/llvm-commits at cs.uiuc.edu/msg14069.html > * llvm-gcc --v...

...ination register is also used as source register. In 2007 a patch was discussed at the mailing list, however my compiler still is producing this result. Does anyone know if this patch is actually applied? * I use the following arguments: llvm-gcc -mfpu=vfp -mlittle-endian -mfloat-abi=softfp -march=armv5 -S -O3 foo.c -S -o foo.s * Attached to this document foo.c and the resulting foo.s. Please, take note of the illegal instruction mul r0, r0, r2 at line 18. * The patch is discussed at: http://www.mail-archive.com/llvm-commits at cs.uiuc.edu/msg14069.html * llvm-gcc --version llvm-gcc (GCC) 4.2.1 (B...

...free to look me up at any time during the conference and I'd be happy to talk about the arm backend. Jim On Nov 16, 2011, at 7:24 AM, Joe Abbey <jabbey at arxan.com> wrote: > I'll be attending the hacking session with the intent of understanding what needs to be done to improve ARMv5 Thumb support. With any amount of luck, we can start pounding away at the support. > > My initial understanding from the release notes are that http://llvm.org/bugs/show_bug.cgi?id=1388 has to be fixed first. > > Evan Cheng writes this in 2007: > The proper fix is to model CC as...

I'll be attending the hacking session with the intent of understanding what needs to be done to improve ARMv5 Thumb support. With any amount of luck, we can start pounding away at the support. My initial understanding from the release notes are that http://llvm.org/bugs/show_bug.cgi?id=1388 has to be fixed first. Evan Cheng writes this in 2007: The proper fix is to model CC as explicit register(s). The...

On 22 June 2011 11:49, Damjan Marion <damjan.marion at gmail.com> wrote: > # /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c Even though you specified cpu as arm9, it's probably generating generic ARM IR (use -emit-llvm -S and see), which defaults to ARM instructions. If you want thumb, use triple =

...ive in and build my own Samba server. And I have a few questions. All of my servers will be ARM. The main hardware will be Cubieboards (2 and truck). They will be running Centos-7 once the development is finished. For now I am using Fedora 22 arm. My backup file server will be a pogoplug (armv5) with Redsleeve 7.1. My current environment is ClearOS with a handful of XP systems with roaming profiles. Of course this is an Intel server. So on to some questions... I am reading an old how to I pulled a year? ago: WIP_Beginner HowTo - SOHO business server - SambaWiki.html And it says IP...

...* With post processing (deblocking/deringing) enabled, this drops to 23fps. * Uses no hardware acceleration features (e.g. dithered YUV2RGB is done in software, so on devices with such features available, it could go even faster). * Uses ARMv4 instructions only (no reliance on Xscale SIMD or ARMv5/v6/v7/NEON). * Compatible with films encoded with the latest encoder versions. For more information, see the website above, or contact me. Robin -- Robin Watts, Email: <mailto:Robin.Watts at wss.co.uk> Warm Silence Software, WWW: <http://www.wss.co.uk/> P.O.Box 28,...

...I have a few questions. >> >> All of my servers will be ARM. The main hardware will be Cubieboards >> (2 and truck). They will be running Centos-7 once the development is >> finished. For now I am using Fedora 22 arm. My backup file server >> will be a pogoplug (armv5) with Redsleeve 7.1. >> >> My current environment is ClearOS with a handful of XP systems with >> roaming profiles. Of course this is an Intel server. >> >> So on to some questions... >> >> I am reading an old how to I pulled a year? ago: >> >&g...

...n at gmail.com> wrote: > Problem is that in case when old binutils are used (in my case freebsd is using old one due to license upgrade to GPLv3) AS doesn't understand new mnemonics and fails. Indeed, this is new in ARM ARM v7. > Can we change to old mnemonic at least when ARMv4 and ARMv5 code is generated? We definitely should. Feel free to send a patch if you already have, or create a bug in bugzilla. Shouldn't be too hard to add it. cheers, --renato