search for: mblaze

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 triple support in include/llvm/ADT/Triple.h and lib/Support/Triple.cpp 4. Adds mblaze backend support in lib/Target/MBlaze 5. Adds mblaze te...

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: err...

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 ARMELFObjectWri...

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...

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, folk...

Hello, this is a very dump question, I hope to do more valuable question soon, but for now I'm just trying to run a simple hello world in C for clang and llvm to the target mblaze, but is not working. ( I need to change the compiler in the next stage) I past all the weekend tried to run this, and I was unable, I did the build of llVM/clang, but no bin was generate, only silly folder that I don't know for what can be useful. Can you please recommend me some tutorials o...

> > 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 a...

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...

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 are having to...

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

...ilinx 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 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. Curre...

I just tried cmake for the first time and it mostly worked. I had been using autotools to configure. With cmake configure environment when I try to do: make TESTSUITE=CodeGen/mblaze check it runs the whole test suite. Under autotools it would just run the mblaze tests. Is there an equivalent command in a camke configured environment or is this broken? I know nothing about cmake so I'm hoping there is a trivial answer. JP

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 mainta...

...ackend. > > 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 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...

...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 > <mailto: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....

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 him are bouncing. > > > I propose to remove the MBlaze backend on Friday if none step > for...

> 5. I could just add the MBlaze backend specific stuff into ELFObjectWriter > like all of the other backends. > Are their any other opinions on this? I personally prefer all of the MBlaze > backend stuff to be contained inside of lib/Target/MBlaze so that I don't > have to hunt around the LLVM source tree when I...

...Thanks for the suggestion. I recompiled with Debug+Asserts and it shows that the unreachable is in CallingConvLower.cpp:162. Here is the error message: Call result #2 has unhandled type f32UNREACHABLE executed at CallingConvLower.cpp:162! I don't think my backend is modified enough from the MBlaze backend that is in the release to be causing this error. I am however looking through the various files of the backend to try to find where the calling convention might be causing problems with f32 data types. Josef -------------- next part -------------- An HTML attachment was scrubbed... URL: &l...

Hi Rogelio, Glad to see MBlaze will not be removed. I suggest you put your name on CODE_OWNERS.TXT. ;) Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

...riginal Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Eric Christopher > Sent: Wednesday, July 24, 2013 2:10 PM > To: peckw at wesleypeck.com > Cc: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] Deprecating and removing the MBlaze backend > > 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. > > Th...