search for: armv5e

On 26 February 2013 16:14, David Blaikie <dblaikie at gmail.com> wrote: > I'm not sure I understand your question. Fail tests continue to run so we > find out if they start passing as seems to be the case here. If llvm is 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

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

Current llvm svn fails make check when built for only x86... [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.3/build/bin/./llc -O0 <

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

I hope this is addressed by r177545 - please let me know if this test is still failing for you after that change. On Wed, Mar 20, 2013 at 8:38 AM, David Blaikie <dblaikie at gmail.com> wrote: > 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

On 18 May 2013 19:29, David Tweed <David.Tweed at arm.com> wrote: > Regarding solving PR16013 that looks like a relatively tractable job (on > both 32-bit arm and aarch64) IF you're already familiar with the > implications of what the instruction set does; unfortunately that set > doesn't include me... > Hi David, I'll move all remote tests to a dir and mark

On Jun 22, 2011, at 3:16 PM, Renato Golin wrote: > 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

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

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>

Hi, > I am using a cross compiler to compiler for the arm5 architecture. For this > architecture it is not allowed that a destination 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:

Hi, I am using a cross compiler to compiler for the arm5 architecture. For this architecture it is not allowed that a destination 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

Hi Joe, Not sure yet if I'll be able to make the hacking session or not, but either way, feel 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

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

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 =

After years of delays and side trips, I really am going to dive 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

This is a note to announce the availability of "Ogg Theorarm", an optimised ARM implementation of decoding libraries for the Theora video code, and Vorbis audio codec from xiph.org. Full details of this code release can be found at <http://www.wss.co.uk/pinknoise/theorarm>, but highlights include: * Full speed playback of a 320x240x25fps clip with a 48kHz stereo audio track on

thanks for the reply. On 08/23/2015 01:26 PM, Rowland Penny wrote: > On 23/08/15 17:10, Robert Moskowitz wrote: >> After years of delays and side trips, I really am going to dive 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

On 22 June 2011 14:33, Damjan Marion <damjan.marion 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.