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 with no help. -Chandler -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130205/301feb37/attachment.html>
On 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, folks are having to keep it up to date when changing shared parts of the backend with no help.Hi Chandler, This seems entirely reasonable. Thanks, Jim
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, folks are having to keep it up to date when changing > shared parts of the backend with no help. >+1
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, folks are having to keep it up to date when changing > shared parts of the backend with no help. >I just want to clarify: there is no actual problem with the MBlaze backend, and this isn't a trap. ;] It's a really nice backend, the code quality is fine, we just need an active maintainer to help fix issues and keep it up to date as the code generator layer evolves. =] Hopefully someone is interested in getting involved in the community here and contributing to the backend. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130205/d565539d/attachment.html>
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 > <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. Currently, folks are having to keep it up > to date when changing shared parts of the backend with no help. > > > I just want to clarify: there is no actual problem with the MBlaze > backend, and this isn't a trap. ;] It's a really nice backend, the code > quality is fine, we just need an active maintainer to help fix issues > and keep it up to date as the code generator layer evolves. =] Hopefully > someone is interested in getting involved in the community here and > contributing to the backend. > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On Feb 6, 2013 4:52 AM, "Chandler Carruth" <chandlerc at gmail.com> wrote:> > The MBlaze backend seems to be essentially unmaintained since 2011. Themaintainer (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 asa maintainer. Currently, folks are having to keep it up to date when changing shared parts of the backend with no help.> > -Chandler > >Hi i have a new customer who needs it. I'm interested in maintaining it myself. I need to step up quickly though because i haven't even looked at the backend since 2011. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130206/36d58bf6/attachment.html>
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
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 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 keep it up to date when > changing shared parts of the backend with no help. > > > > -Chandler > > > > > > Hi i have a new customer who needs it. I'm interested in maintaining it > myself. > > I need to step up quickly though because i haven't even looked at the > backend since 2011. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130208/183b0a4a/attachment.html>
Fernando Herrera via llvm-dev
2015-Sep-21 11:28 UTC
[llvm-dev] The MBlaze backend: can we remove it?
Chandler Carruth <chandlerc <at> gmail.com> writes:> > The MBlaze backend seems to be essentially unmaintained since 2011. Themaintainer (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 asa maintainer. Currently, folks are having to keep it up to date when changing shared parts of the backend with no help.> >Dear Mr Carruth, I am Fernando Herrera. I work for the University of Cantabria (Spain). We are interested in the microblaze branch of LLVM (preferently as users). Do you know if there is any available (even if unofficial or out of the tree) branch which could work with LLVM 3.5 (or later)? Maybe somebody in Xilinx? Eventually, we could update it to make it work with later LLVM versions, as long as we can afford that cost. Many thanks in advance for any information you can give to us. Best Fernando> -Chandler > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev <at> cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Richard Pennington via llvm-dev
2015-Sep-22 01:30 UTC
[llvm-dev] The MBlaze backend: can we remove it?
On 09/21/2015 06:28 AM, Fernando Herrera via llvm-dev wrote: [snip]> Dear Mr Carruth, > > I am Fernando Herrera. I work for the University of Cantabria (Spain). > We are interested in the microblaze branch of LLVM (preferently > as users). > > Do you know if there is any available (even if unofficial > or out of the tree) branch which could work with LLVM 3.5 (or later)? > > Maybe somebody in Xilinx? > > Eventually, we could update it to make it work with > later LLVM versions, as long as we can afford that cost. > > Many thanks in advance for any information you can give to us. > > Best > > FernandoHi Fernando, I've been pseudo-maintaining the Microblaze code generator since it was removed. It does compile, with recent TOT LLVM (last update was to LLVM r247783), Unfortunately, over time it has stopped being fully working, even for C (C++ needs some atomic work as I recall). I suspect getting it functional again wouldn't be too hard, I just haven't had time. I tried to get someone at Xilinx interested in it, since maintaining it, even to just keep compiling, takes a bit of time. They didn't seem to be interested, and the only reason I've been keeping it up is that I seem to have a stubborn streak. If you're interested, the code is at http://ellcc.org. Best regards, Rich