search for: softcore

Hello Sébastien, Making backends to LLVM is a significant amount of work. If you want somebody to do it for you, either offer some payment or do your own coding. Keep in mind that the bread-and-butter support for LLVM comes from Apple computer so unless the next iPad will start using softcores, be prepared to pursue the other courses of action I laid out. I may be having to write a backend to the N68050 softcore soon but am busy writing my own LLVM-based compiler at the moment so don't expect me to jump up and down with excitement just because there is a new softcore that doesn'...

On Monday 24 May 2010 14:32:19 Eli Friedman wrote: > Resending the email isn't really productive; for the given question, > the lack of a reply should answer your question. Was there something > else you wanted to ask? I find this message unhelpful at best, if not purely arrogant. You are making an open source compiler, I am making an open source processor: we are fighting for the

On Mon, May 24, 2010 at 2:11 AM, Sébastien Bourdeauducq <sebastien.bourdeauducq at lekernel.net> wrote: > Just bringing that up as I did not get any reply so far. Resending the email isn't really productive; for the given question, the lack of a reply should answer your question. Was there something else you wanted to ask? -Eli > Thanks, > Sébastien > > > On Tuesday

Hi, does anyone have small programms in C, one to encode and one to decode with celt, that I could use for a fpga chip softcore? greets yon -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20100819/7cd96a41/attachment-0002.htm

...backend into LLVM. We need community feedback and reviewers for patches which we will submit soon. AAP was designed in early 2015 and aims to advance compiler development for small deeply embedded Harvard architectures, which are widely used commercially. AAP is freely available as an open source softcore for use in FPGA designs. AAP has wide exposure: at ORCONF16 at CERN, at FOSDEM and at BCS and OSHUG meetings. It is also of commercial interest, because of the potential benefits of providing upstream LLVM support for features found in small embedded processors. Currently there is a complete Clan...

...ck and reviewers for patches >> which we will submit soon. >> >> AAP was designed in early 2015 and aims to advance compiler development >> for small deeply embedded Harvard architectures, which are widely used >> commercially. AAP is freely available as an open source softcore for use >> in FPGA designs. >> >> AAP has wide exposure: at ORCONF16 at CERN, at FOSDEM and at BCS and >> OSHUG meetings. It is also of commercial interest, because of the >> potential benefits of providing upstream LLVM support for features found >> in small emb...

...ck and reviewers for patches >> which we will submit soon. >> >> AAP was designed in early 2015 and aims to advance compiler development >> for small deeply embedded Harvard architectures, which are widely used >> commercially. AAP is freely available as an open source softcore for use >> in FPGA designs. >> >> AAP has wide exposure: at ORCONF16 at CERN, at FOSDEM and at BCS and >> OSHUG meetings. It is also of commercial interest, because of the >> potential benefits of providing upstream LLVM support for features found >> in small emb...

Hi David, What kind of "a lot of out-of-tree changes"? You should push changes incrementally as you do work. Holding onto changes means that many things, not just reformatting, can make them need to be redone. We frequently clean up and rewrite code to make it cleaner and easier to maintain. We are moving to a more strict internal review and pushing of changes and post commit

On Dec 22, 2007, at 2:40 AM, Richard Pennington wrote: > Does Elsa provide an advantage over g++? For me, understanding it is a > big plus. ;-) In addition, Elsa has a Berkeley-like license which I > prefer. Ok. If you're not planning on extending the front-end, understandability doesn't really matter ;-). I get where you're coming from though! > Since I only

Chris Lattner wrote: > On Dec 21, 2007, at 1:08 PM, Richard Pennington wrote: > >> I'm a little further along now. I've started to put together a simple >> driver for Elsa and LLVM that I'm calling "ellsif" (cute name, I think >> it works). >> >> The file being compiled is a "printf" function. Here are timing >> results

folks hi, something i just wanted to double-check. is it possible to use, with LLVM, entirely free software tools to build and upload to a xilinx microblaze FPGA target? i take some c code, put it through llvm-fpga, aaand... then what? is there any documentation about this stuff, anywhere? tia, l.

...>> LLVM code generator for the Altera Nios2. ;-) I started by copying the >> MIPS sources and am studying them to get a feel for what's required. > > Ah, nifty. I no nothing of that processor, but you can build a > backend independent of the front-end :) The Nios2 is a softcore processor running in Altera FPGAs. Very MIPS like. Being soft, the instruction set can be extended as can the hardware. In software. Very cool. -Rich

> I've build gcc many times over the years for different target processors > and was never able to get my head around it internally. It is incredibly > complex. I also didn't like the fact that I had to have N copies of gcc > to support N processors. Scott McPeak is rather familiar with the internals of gcc and edg and says elsa is far simpler. > I became interested in

...MIPS sources and am studying them to get a feel for what's required. > > In other words you want a C++ compiler for the Nois2? No, g++ exists for the Nios2. Altera has a port. I am interested working with some language stuff that might be cool in an embedded environment. The Nios is a softcore processor that runs on Altera FPGAs. A programmable processor. Think of what kind of optimizations that might allow. > > Daniel > > -Rich

...patches for review. I intend to in the new year (and I've already mentioned this to Jack and Vladimir), but only the ones that are relevant for other MIPS consumers. Given the large number of non-standard extensions to MIPS that abound now (and this will only increase when we open source our softcore in the new year), I imagine that there will be no shortage of other MIPS-based back ends being maintained out of tree. The poor modularity in the existing code makes it difficult to upstream these, although I've been (very slowly) working on fixing that in our branch. David ________________...