similar to: [LLVMdev] The MBlaze backend: can we remove it?

Hi, I just saw this thread. I work on llvm at Xilinx but I do not work on microblaze. I will check to see if there is any interest here at Xilinx to contribute resources to the maintenance of this backend. Thanks, Jeff On Tue, Feb 5, 2013 at 7:38 PM, Rogelio Serrano <rogelio.serrano at gmail.com>wrote: > > On Feb 6, 2013 4:52 AM, "Chandler Carruth" <chandlerc at

Hi jeff! Any news? On Feb 9, 2013 1:53 AM, "Jeff Fifield" <fifield at mtnhigh.net> wrote: > Hi, > > I just saw this thread. I work on llvm at Xilinx but I do not work on > microblaze. > > I will check to see if there is any interest here at Xilinx to contribute > resources to the maintenance of this backend. > > Thanks, > Jeff > > > > On

On Feb 6, 2013 4:52 AM, "Chandler Carruth" <chandlerc at gmail.com> wrote: > > The MBlaze backend seems to be essentially unmaintained since 2011. The maintainer (Wesley Peck who is BCC'ed) seems to have vanished, and in fact all emails to him are bouncing. > > I propose to remove the MBlaze backend on Friday if none step forward as a maintainer. Currently, folks

> > The MBlaze backend seems to be essentially unmaintained since 2011. The > maintainer (Wesley Peck who is BCC'ed) seems to have vanished, and in fact > all emails to him are bouncing. > I propose to remove the MBlaze backend on Friday if none step forward as a > maintainer. Currently, folks are having to keep it up to date when changing > shared parts of the backend

I think you should wait until it becomes a problem. Xilink is actively hiring for LLVM people so maybe it will get some use again soon. I get at least one email a day from their head hunters. http://en.wikipedia.org/wiki/MicroBlaze On 02/05/2013 01:02 PM, Chandler Carruth wrote: > > > > On Tue, Feb 5, 2013 at 12:52 PM, Chandler Carruth <chandlerc at gmail.com >

On Tue, Feb 5, 2013 at 12:52 PM, Chandler Carruth <chandlerc at gmail.com>wrote: > The MBlaze backend seems to be essentially unmaintained since 2011. The > maintainer (Wesley Peck who is BCC'ed) seems to have vanished, and in fact > all emails to him are bouncing. > > I propose to remove the MBlaze backend on Friday if none step forward as a > maintainer. Currently,

On Tue, Feb 5, 2013 at 3:50 PM, Preston Briggs <preston.briggs at gmail.com>wrote: > The MBlaze backend seems to be essentially unmaintained since 2011. The >> maintainer (Wesley Peck who is BCC'ed) seems to have vanished, and in fact >> all emails to him are bouncing. > > >> I propose to remove the MBlaze backend on Friday if none step forward as >> a

I have been working on a LLVM backend for the MicroBlaze soft-processor: http://www.xilinx.com/tools/microblaze.htm http://en.wikipedia.org/wiki/MicroBlaze Attached is the initial MicroBlaze patch. It does the following: 1. Adds mblaze as a target in configure and configure.ac 2. Adds mblaze specific intrinsics in include/llvm/IntrinsicsMBlaze.td and include/llvm/Intrinsics.td 3. Adds mblaze

On 02/05/2013 03:58 PM, Chandler Carruth wrote: > On Tue, Feb 5, 2013 at 3:50 PM, Preston Briggs <preston.briggs at gmail.com > <mailto:preston.briggs at gmail.com>> wrote: > > The MBlaze backend seems to be essentially unmaintained since > 2011. The maintainer (Wesley Peck who is BCC'ed) seems to have > vanished, and in fact all emails to

The Sparc, Microblaze, and Mips code generators implement branch delay slots. They all seem to exhibit the same bug, which is not surprising since the code is very similar. If I compile code with this snippit: while (n--) *s++ = (char) c; I get this (for the Microblaze): swi r19, r1, 0 add r3, r0, r0 cmp r3, r3, r7 beqid r3,

Is it kosher to include vim mode line comments inside of LLVM source files? I would like to do this inside of the MicroBlaze backend to ensure that tabs are expanded into exactly two spaces. I see that right now the following files have these vim mode line comments: include/llvm/ADT/SetVector.h lib/Archive/ArchiveInternals.h lib/Linker/LinkModules.cpp lib/Transforms/IPO/DeadTypeElimination.cpp

Hi, I've been working on combining LLVM, clang, the NetBSD standard C library, compiler-rt, QEMU, GDB, and GNU binutils as a cross compilation environment. My goal is to target small embedded systems, but I think that what I'm working on may be of interest to other LLVM/clang developers as I have been able to use the environment to fix several code generation issues in LLVM. As of

On 17 January 2011 10:30, Richard Pennington <rich at pennware.com> wrote: > * It is currently based on a fairly recent version of LLVM/clang: r122956. This is great. I've noticed that you've made some fixes or additions that haven't made it upstream yet, such as the Microblaze parameter fix in rev 2337 (CCed Wesley Peck as he seems to have done a lot of work on the MBlaze

Doesn't seem to get a lot of love since most of the commits in the last 3 years have been maintenance. I guess it doesn't take a whole lot of maintenance either, but... cc'ing Wesley since he seems to be the last guy to commit to it. Thoughts? -eric

On Dec 14, 2010, at 3:46 PM, Richard Pennington wrote: > Notice that the label $BB0_1 is missing. If I disable filling in the > branch delay slots, I get: Is this with the latest SVN HEAD version of LLVM or some other version? The delay slot filler and many other things have been updated for the Microblaze backend. In particular, the commit r120095 for the MBlaze backend fixed some issues

On 12/14/2010 04:28 PM, Wesley Peck wrote: > On Dec 14, 2010, at 3:46 PM, Richard Pennington wrote: >> Notice that the label $BB0_1 is missing. If I disable filling in the >> branch delay slots, I get: > > Is this with the latest SVN HEAD version of LLVM or some other version? The delay slot filler and many other things have been updated for the Microblaze backend. In

Hello, i am trying to create a LLVM stack to cross compile c code targeting the xilinx microblaze. I built LLVM configured with target=microblaze however cland doesn't like it. When i try to emit llvm code i get the following error: unknown target triple 'microblaze-unknown-none', please use -triple or -arch How should i configure my LLVM stack and then how should i run the tools

Hi Fivos, LLVM refers to the target as "mblaze" for -target. -Jim On Jun 26, 2012, at 8:42 AM, Fivos <fivosz at gmail.com> wrote: > Hello, > > i am trying to create a LLVM stack to cross compile c code targeting the > xilinx microblaze. > > I built LLVM configured with target=microblaze however cland doesn't > like it. When i try to emit llvm code

I have been working on getting ELF object file writing working for the MBlaze backend. Currently, each supported backend calls ELFObjectWriter::createELFObjectWriter from within the backend's TargetAsmBackend::createObjectWriter method. The createELFObjectWriter method then creates a new backend specific ELFObjectWriter class (either X86ELFObjectWriter or ARMELFObjectWriter) by decoding a

conmfigure does not accept mblaze nor mblaze-elf as target. checking target system type... Invalid configuration `mblaze': machine `mblaze' not recognized configure: error: /bin/bash ../../spare/llvm/autoconf/config.sub mblaze failed However with microblaze it proceeds fine. But when i try to use clang i get: clang: error: 'microblaze-unknown-none': unable to pass LLVM bit-code