similar to: [LLVMdev] LLVM on small MCUs?

John Regehr wrote: > I ask since gcc is causing significant pain for one of my students. He > could switch over to LLVM but only after writing a backend for AVR (8-bit > RISC). An AVR backend would be very cool. AVR is way more compiler friendly than PIC, so it should not be all that difficult either. The only hitch is that in the MCU world people expect to be able to write interrupt

On Mon, 2008-05-19 at 20:40 +0300, Pertti Kellomäki wrote: > The only hitch is that in the MCU world people expect to be > able to write interrupt handlers and the like in C... Most of the support that I have seen for this in other compilers amounts to custom calling conventions and preambles. Are you thinking of more than this?

Anyone else interested in an AVR backend? If so, for what members of the AVR family? If we do a port, likely it'll support only the ATmegas. John

I have a client who might well make use of an AVR32 port, but I suspect that machine is very different than the one you are currently examining. shap On Mon, 2008-05-19 at 12:38 -0600, John Regehr wrote: > Anyone else interested in an AVR backend? > > If so, for what members of the AVR family? If we do a port, likely it'll > support only the ATmegas. > > John >

There is an email thread under llvm-commits titled: [llvm-commits] PATCH for PIC16 target. One of the replies to this thread explains some of the challenges that we are facing on PIC16 Ali. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of John Regehr Sent: Monday, May 19, 2008 9:45 AM To: llvmdev at cs.uiuc.edu Subject:

> [llvm-commits] PATCH for PIC16 target. Do you have a link? Google isn't turning this up. I'd be interested in hearing more about this experience... Thanks, John

> Do you have a link? Google isn't turning this up. http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062319.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL:

GCC for AVR is awesome but, as far as I know, until very little time ago, compiler support for PIC was close to none. 2008/5/19 Jonathan S. Shapiro <shap at eros-os.com>: > I have a client who might well make use of an AVR32 port, but I suspect > that machine is very different than the one you are currently examining. > > > shap > On Mon, 2008-05-19 at 12:38 -0600, John

>> Do you have a link? Google isn't turning this up. >http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062319.html Wow, PIC looks like a brutal port. AVR would be easy in comparison: stack-based architecture with plenty of registers. However, these architectures share: - 8-bit loads, stores, and arithmetic ops. - Harvard architecture What sizes and

> I have a client who might well make use of an AVR32 port, but I suspect > that machine is very different than the one you are currently examining. I have not looked at AVR32 closely but my understanding is that it is a new architecture that shares a substring with AVR for marketing reasons. John

Is anyone working on supporting additional targets used in embedded systems. I am particularly interested in two: 1. TI MSP430. http://en.wikipedia.org/wiki/TI_MSP430 A nice very low power 16-bit machine with a PDP-11-like instruction set. We can assume the PIC16 developers have found and fixed all the 32-bit assumptions in the code base. Newer versions, the MSP430X series, have

I am interested in developing a backend for the PIC microcontrollers. Specifically, I plan to write for the 8-bit MCUs, but would hopefully also support the 16 and 32 bit models (eventually). It is my understanding that a backend for PIC16 was previously a part of the project but was dropped in version 2.9. Is there any development on this front currently? Is there any interest in developing this

I've been looking closely at LLVM as a means to developing a new toolchain for an MCU core of very similar architecture. To that end, the once included PIC16 backend might be a valuable reference. I found a message in April of this year that indicated it had been dropped from new releases however, and that were it to be resumed "it will be largely a rewrite". I'm wondering if

On Sep 20, 2011, at 10:59 PM, Matthew Hilt wrote: > I've been looking closely at LLVM as a means to developing a new toolchain for an MCU core of very similar architecture. To that end, the once included PIC16 backend might be a valuable reference. I found a message in April of this year that indicated it had been dropped from new releases however, and that were it to be resumed "it

Thank you for both of your input. Yes, I try to cross-compile for AVR, the simple ATMEGA328P used in every Arduino Uno. My main motivation being that I hope to be able to use a couple of STL containers, <functional> and <type_traits> on the MCU. Not sure though if this can be reached by going via the clang route. Getting back to the compilation: when I run clang with both both

I'm beginning to use the AVR backend. I ran into the problem, that newer (tiny1, mega0) µC as a tiny1614 are not supported. How do I add these to the AVR backend? Thanks!

Hi folks, We recently generated some data that seemed interesting enough to share here. This is a comparison between compilers that ignores the performance of the generated code and focuses only on compiler correctness. volatile checksum errors errors avr-gcc-3.4 1.879% 0.378% avr-gcc-4.1 0.037% 0.256% avr-gcc-4.2

Thanks! The new are of xmega3 architecture, which is already included. So this should be simple. Where is the information about ISR-vector table, SRAM addresses and so on stored? -- Wilhelm Am 04.03.20 um 11:03 schrieb Dylan McKay: > Hey Wilhelm, > > This should be possible by editing the 'AVRDevices.td' [1]TableGen > definitions to add an entry for the newer chip types.

Hi everyone, I've been wondering how to correctly build clang/LLVM for the AVR target architecture. Unfortunately documentation is very scarce (or outdated or I didn't find it) and while I've been able to build clang/LLVM for AVR I'm still falling short of compiling an actual binary for the MCU. Here are the steps I've undertaken so far: git clone

On Sep 21, 2011, at 2:53 PM, Dan Gohman wrote: > On Sep 20, 2011, at 10:59 PM, Matthew Hilt wrote: > >> I've been looking closely at LLVM as a means to developing a new toolchain for an MCU core of very similar architecture. To that end, the once included PIC16 backend might be a valuable reference. I found a message in April of this year that indicated it had been dropped from