search for: mbeds

...nderstood, this tests run completely on the target > (compilation of LLVM, unit tests, etc). So, for bare-metal tests that > wouldn't work. We'd need to have a staging server that would compile > to all platforms and run the tests (maybe just a subset) in the > hardware via USB (mBeds) or JTAG on most other boards, or even better, > on models directly. > > Do you think this is doable with the build bot infrastructure? > > cheers, > --renato > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu  ...

..., >From what I understood, this tests run completely on the target (compilation of LLVM, unit tests, etc). So, for bare-metal tests that wouldn't work. We'd need to have a staging server that would compile to all platforms and run the tests (maybe just a subset) in the hardware via USB (mBeds) or JTAG on most other boards, or even better, on models directly. Do you think this is doable with the build bot infrastructure? cheers, --renato

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:

Hello all, I noticed that for ARM Thumb target, llc uses r7 as frame pointer (gcc does not do this AFAIK), and this register should therefore not be used as a general-purpose register. However, when compiling mbedTLS, which contains some code that is highly optimized for ARM platform and uses r7 to efficiently perform an operation. This raises an exception since r7 is now the frame pointer. I

Am 19.12.2014 11:00, schrieb Renato Golin: > On 18 December 2014 at 04:02, Tim Northover <t.p.northover at gmail.com> wrote: >>> You have some special version of qemu? My default distribution's qemu >>> package did not have a cortex-M0 nor has qemu head freshly taken from git: >> The trouble with Cortex-M0 (from a virtualised testing perspective) is >>

On 18 December 2014 at 04:02, Tim Northover <t.p.northover at gmail.com> wrote: >> You have some special version of qemu? My default distribution's qemu >> package did not have a cortex-M0 nor has qemu head freshly taken from git: > > The trouble with Cortex-M0 (from a virtualised testing perspective) is > that it doesn't have an MMU, so any "real"

Hi all, I'm wondering if the GPL-2.0 licensed mbedTLS (that's the version in OpenWrt) is 'compatible' with NUT binaries (not including the Python or Perl binaries which aren't used in OpenWrt) which is GPL 2.1+ AIUI. Because mbedTLS is the default library for OpenWrt and NSS is not yet in OpenWrt, and because OpenSSL is considered incompatible (I seem to recall reading that