similar to: [LLVMdev] Standalone use of compiler-rt for ARM

On Sun, Jul 22, 2012 at 11:12 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 22 July 2012 22:03, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> While we are at it, if a new comer would like to understand where everything >> takes place, where should he look? >> >> I did a grep in the source and eventually ended up in

On Sun, Jul 22, 2012 at 9:42 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Any suggestions? > Try to specify CPU explicitly. Already did. clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3 fatal error: error in backend: CPU: 'cortex-m3' does not support ARM mode execution! S.

> clang++ -ccc-gcc-name arm-none-linux-gnueabi-g++ -ccc-host-triple > thumbv7m-none-gnueabi testReference.cpp -c -mcpu=cortex-m3 > fatal error: error in backend: CPU: 'cortex-m3' does not support ARM > mode execution! Ok, and what's about -mthumb then? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Wed, Jul 18, 2012 at 3:52 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 14:33, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> but I still haven't figure out how to build for cortex-m3 >> >> clang -march=armv7-m -mfloat-abi=soft <something missing?> testReference.cpp -c > > -march should have done

Dear Speex developers I am going to port Speex on LPC2368 I tested Speex encoding and the mesurments shows ~40ms cpu time for one frame Do you know who ported speex to NXP or other 32bit platform? Best Regards Zohar fox -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20081105/8261e962/attachment.htm

Hello, I want to build LLVM/Compiler-rt for baremetal targets like Cortex-M3. By adopting CMake options from http://llvm.1065342.n5.nabble.com/llvm-dev-Compiling-for-baremetal-ARMv4-on-Ubuntu-Linux-tp124226p124500.html, I can only build "libclang_rt.builtins-x86_64.a" in lib/linux, but what I want to build is "libclang_rt.builtins.arm.a". My CMake options are: cmake -G Ninja

On 22 July 2012 22:03, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > While we are at it, if a new comer would like to understand where everything > takes place, where should he look? > > I did a grep in the source and eventually ended up in clang/something/driver. That's pretty much it: clang/lib/Driver

Hello, since I had delayed the programming of the UPS Device part, now it is time to continue... My Device is "24 V DC modular ATX PSU" which replace the standard ATX Power Supply in PCs and use 15-43 V Input Voltage. The microcontroller is a TI LM3S5T36 Cortex M3 and I get the "UPS" infos using up to 4 Maxim DS1780 and some I?C current sensors. The ATX PSU has 4

Hi there, I'm trying to switch from GCC to llvm (clang++) for cross-compiling a firmware of mine for a stm32 (ARM cortex-m3). After looking in the documentation and a bit of googling here is what I did (in case someone else in the future is having the same problem) cd llvm git clone http://llvm.org/git/llvm.git cd llvm/tools git clone http://llvm.org/git/clang.git cd llvm/projects git

Hello, Since I have now nearly all stuff running on my LH7A404 and now I am working on my DS80C411, I like to know, whether NUT show the APC UPS stats like the APC tools. Currently I do not know, HOW NUT triber the USB-Poert to get out the infos of the UPS. In theory I do send out only arround 5-60 lines of data which then NUT or any other programs must parse or something

I purchased a Code Red RDB1768v2r3 Rev B1 board. I'm trying to use the NXP provided example for the Speex codec from App Note: NXP AN11085 http://ics.nxp.com/support/documents/microcontrollers/zip/an11085.zip Does this example application run reliably on the Code Red RDB1768v2r3? Is there a modified version of Speex available that is fully functional? When

Hi there, I'm trying to switch from GCC to llvm (clang++) for cross-compiling a firmware of mine for a stm32 (ARM cortex-m3). After looking in the documentation and a bit of googling here is what I did (in case someone else in the future is having the same problem) cd llvm git clone http://llvm.org/git/llvm.git cd llvm/tools git clone http://llvm.org/git/clang.git cd llvm/projects git

On 18 July 2012 14:33, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > but I still haven't figure out how to build for cortex-m3 > > clang -march=armv7-m -mfloat-abi=soft <something missing?> testReference.cpp -c -march should have done the trick. You can also try -mcpu=cortex-m3, or try -ccc-host-triple armv7m-none-gnueabi (or -eabi), and possibly

On Darwin, if -march is armv7 clang's driver will assume you want thumb2 unless you also give it -mno-thumb but that is irrelevant with mcpu=cortex-m3. I agree its a mess. -Chris On Jul 22, 2012, at 4:37 PM, Renato Golin wrote: > On 22 July 2012 20:42, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>> Any suggestions? >> Try to specify CPU explicitly. >

Hi Jan, For Cortex-M0, you should probably use the armv6m string in the target triple. For M3 and M4 you need to use the thumbv7m arch string, -mthumb won't be necessary. Amara On 11 October 2013 19:23, Jan Hoogerbrugge < jan.hoogerbrugge at biface-tools.com> wrote: > Hi, > > I am trying to cross compile code for ARM Cortex m0, m3, and m4. > > For m0, I use: > >

Hi, I am trying to cross compile code for ARM Cortex m0, m3, and m4. For m0, I use: -target armv6--eabi -mcpu=cortex-m0 That seems to work. For m3 and m4, I use the following which does not work (fatal error: error in backend: CPU: 'cortex-m3' does not support ARM mode): -target armv7m--eabi -mcpu=cortex-m3 and -target armv7em--eabi -mcpu=cortex-m4 Who can help me with the

On Mon, 21 Dec 2009 21:00:01 +0100, <speex-dev-request at xiph.org> wrote: > Thank you for your product Speex. We want to use it in > microcontroller AT91SAM7S256 (48 MHz). I'd strongly advice to use a higher performance micro. Let's consider that you'd succeed in getting it working right after optimizations. The time you want to add other speex features or other

Looks OK to me, but I don't have any Cortex-M3 docs to confirm the choice of v7-A without NEON. deep On Sun, Nov 22, 2009 at 9:47 PM, Bagel <bagel99 at gmail.com> wrote: > Here is a one-line patch to support the cortex-m3. > For those who plan the features for ARM, the new cortex-m0 implements only a > subset of the Thumb2 instructions.  I still have yet to see a document that

> > $ qemu-arm -cpu ? > > Available CPUs: > > arm926 arm946 arm1026 arm1136 arm1136-r2 arm1176 arm11mpcore > > cortex-m3 > > cortex-a8 > > cortex-a8-r2 cortex-a9 cortex-a15 ti925t pxa250 sa1100 sa1110 > pxa255 pxa260 > > pxa261 pxa262 pxa270 pxa270-a0 pxa270-a1 pxa270-b0 pxa270-b1 xa270- > c0 > > pxa270-c5 any > > >

Making a symlink to clang in the same directory as the GCC / binutils (I'll call it $ARM_BIN) called arm-none-linux-gnueabi-clang (and one with clang++ too) and another link in the $ARM_BIN/../lib directory to clang directory located under clang's lib (for includes) should be enough. Gordon Keiser Software Development Engineer Arxan Technologies gkeiser at arxan.com www.arxan.com