Do you MC support? Cheers, Rafael On Feb 9, 2016 1:12 PM, "Jacques Pienaar via llvm-dev" < llvm-dev at lists.llvm.org> wrote:> > > On Tue, Feb 9, 2016 at 10:05 AM, Chandler Carruth <chandlerc at google.com> > wrote: > >> On Tue, Feb 9, 2016 at 9:58 AM Hal Finkel via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> ----- Original Message ----- >>> > From: "Jacques Pienaar via llvm-dev" <llvm-dev at lists.llvm.org> >>> > To: llvm-dev at lists.llvm.org >>> > Sent: Tuesday, February 9, 2016 11:40:21 AM >>> > Subject: [llvm-dev] [RFC] Lanai backend >>> >>> > Hi all, >>> >>> Hi Jacques, >>> >>> > We would like to contribute a new backend for the Lanai processor >>> >>> I suppose I can guess from your e-mail address who "we" are? >>> >> >> Yep! >> >> >>> >>> > (derived from the processor described in [1]). >>> > Lanai is a simple in-order 32-bit processor with: >>> >>> Can you say a few words about what this is, in what hardware it appears, >>> and how it can be used? Is this the Myricom processor? What version(s)? >> >> >> This is internal hardware for us, so there's not a lot we can share, and >> you can't really grab a version of the hardware. If that's a problem for >> the community, I completely understand. >> >> Mostly, I wanted to offer to upstream this because it seems likely about >> the same utility as the AMDGPU backend for folks without an AMDGPU, or the >> XCore backend, etc. It's small, and we're happy maintaining it and taking >> on any of the effort around it. We're also happy with the usual policy of >> if the maintainers stop showing up, the backend goes away. >> >> But we're working on the backend a bunch, and it didn't make sense to >> keep it walled off. Especially if there is anything that can be reused in >> other backends and/or if there is any common infrastructure we need, this >> makes it easy to test. >> >> Still, totally up to the community if they want this. =] >> >> Aside from the Clang/LLVM support, what other software, drivers, etc. >>> would be needed to make use of this support? What versions of that software? >>> >> >> This is a question for Jacques, I'll let him fill in the details. >> > > Aside from Clang/LLVM support the only other software we use are linker > support in binutils. We have not submitted those yet but it is based on the > previous binutils used (https://github.com/myri/lanai-binutils) but > targeting ELF instead of COFF. > > >> >> -Chandler >> > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/bc0c8ef3/attachment.html>
Yes, we do. But we needed to support linker scripts too else we'd have just used lld. Best, Jacques On Tue, Feb 9, 2016 at 10:20 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote:> Do you MC support? > > Cheers, > Rafael > On Feb 9, 2016 1:12 PM, "Jacques Pienaar via llvm-dev" < > llvm-dev at lists.llvm.org> wrote: > >> >> >> On Tue, Feb 9, 2016 at 10:05 AM, Chandler Carruth <chandlerc at google.com> >> wrote: >> >>> On Tue, Feb 9, 2016 at 9:58 AM Hal Finkel via llvm-dev < >>> llvm-dev at lists.llvm.org> wrote: >>> >>>> ----- Original Message ----- >>>> > From: "Jacques Pienaar via llvm-dev" <llvm-dev at lists.llvm.org> >>>> > To: llvm-dev at lists.llvm.org >>>> > Sent: Tuesday, February 9, 2016 11:40:21 AM >>>> > Subject: [llvm-dev] [RFC] Lanai backend >>>> >>>> > Hi all, >>>> >>>> Hi Jacques, >>>> >>>> > We would like to contribute a new backend for the Lanai processor >>>> >>>> I suppose I can guess from your e-mail address who "we" are? >>>> >>> >>> Yep! >>> >>> >>>> >>>> > (derived from the processor described in [1]). >>>> > Lanai is a simple in-order 32-bit processor with: >>>> >>>> Can you say a few words about what this is, in what hardware it >>>> appears, and how it can be used? Is this the Myricom processor? What >>>> version(s)? >>> >>> >>> This is internal hardware for us, so there's not a lot we can share, and >>> you can't really grab a version of the hardware. If that's a problem for >>> the community, I completely understand. >>> >>> Mostly, I wanted to offer to upstream this because it seems likely about >>> the same utility as the AMDGPU backend for folks without an AMDGPU, or the >>> XCore backend, etc. It's small, and we're happy maintaining it and taking >>> on any of the effort around it. We're also happy with the usual policy of >>> if the maintainers stop showing up, the backend goes away. >>> >>> But we're working on the backend a bunch, and it didn't make sense to >>> keep it walled off. Especially if there is anything that can be reused in >>> other backends and/or if there is any common infrastructure we need, this >>> makes it easy to test. >>> >>> Still, totally up to the community if they want this. =] >>> >>> Aside from the Clang/LLVM support, what other software, drivers, etc. >>>> would be needed to make use of this support? What versions of that software? >>>> >>> >>> This is a question for Jacques, I'll let him fill in the details. >>> >> >> Aside from Clang/LLVM support the only other software we use are linker >> support in binutils. We have not submitted those yet but it is based on the >> previous binutils used (https://github.com/myri/lanai-binutils) but >> targeting ELF instead of COFF. >> >> >>> >>> -Chandler >>> >> >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/a2114974/attachment.html>
That is fine. Lld is an independent project. MC is a core part of llvm and allows codegen (producing a .s) and assembling (producing a .o) to be tested in isolation. So, given that this uses an existing format (ELF) and has MC support, no objections on my side if it includes tests and a description of any peculiarities the architecture has. Cheers, Rafael On Feb 9, 2016 1:23 PM, "Jacques Pienaar" <jpienaar at google.com> wrote:> Yes, we do. But we needed to support linker scripts too else we'd have > just used lld. > > Best, > > Jacques > > On Tue, Feb 9, 2016 at 10:20 AM, Rafael Espíndola < > rafael.espindola at gmail.com> wrote: > >> Do you MC support? >> >> Cheers, >> Rafael >> On Feb 9, 2016 1:12 PM, "Jacques Pienaar via llvm-dev" < >> llvm-dev at lists.llvm.org> wrote: >> >>> >>> >>> On Tue, Feb 9, 2016 at 10:05 AM, Chandler Carruth <chandlerc at google.com> >>> wrote: >>> >>>> On Tue, Feb 9, 2016 at 9:58 AM Hal Finkel via llvm-dev < >>>> llvm-dev at lists.llvm.org> wrote: >>>> >>>>> ----- Original Message ----- >>>>> > From: "Jacques Pienaar via llvm-dev" <llvm-dev at lists.llvm.org> >>>>> > To: llvm-dev at lists.llvm.org >>>>> > Sent: Tuesday, February 9, 2016 11:40:21 AM >>>>> > Subject: [llvm-dev] [RFC] Lanai backend >>>>> >>>>> > Hi all, >>>>> >>>>> Hi Jacques, >>>>> >>>>> > We would like to contribute a new backend for the Lanai processor >>>>> >>>>> I suppose I can guess from your e-mail address who "we" are? >>>>> >>>> >>>> Yep! >>>> >>>> >>>>> >>>>> > (derived from the processor described in [1]). >>>>> > Lanai is a simple in-order 32-bit processor with: >>>>> >>>>> Can you say a few words about what this is, in what hardware it >>>>> appears, and how it can be used? Is this the Myricom processor? What >>>>> version(s)? >>>> >>>> >>>> This is internal hardware for us, so there's not a lot we can share, >>>> and you can't really grab a version of the hardware. If that's a problem >>>> for the community, I completely understand. >>>> >>>> Mostly, I wanted to offer to upstream this because it seems likely >>>> about the same utility as the AMDGPU backend for folks without an AMDGPU, >>>> or the XCore backend, etc. It's small, and we're happy maintaining it and >>>> taking on any of the effort around it. We're also happy with the usual >>>> policy of if the maintainers stop showing up, the backend goes away. >>>> >>>> But we're working on the backend a bunch, and it didn't make sense to >>>> keep it walled off. Especially if there is anything that can be reused in >>>> other backends and/or if there is any common infrastructure we need, this >>>> makes it easy to test. >>>> >>>> Still, totally up to the community if they want this. =] >>>> >>>> Aside from the Clang/LLVM support, what other software, drivers, etc. >>>>> would be needed to make use of this support? What versions of that software? >>>>> >>>> >>>> This is a question for Jacques, I'll let him fill in the details. >>>> >>> >>> Aside from Clang/LLVM support the only other software we use are linker >>> support in binutils. We have not submitted those yet but it is based on the >>> previous binutils used (https://github.com/myri/lanai-binutils) but >>> targeting ELF instead of COFF. >>> >>> >>>> >>>> -Chandler >>>> >>> >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >>> >>> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/93e7e3e9/attachment.html>