[llvm-dev] XCore target

[Nigel Perks via llvm-dev]

Thank you, Chris, it’s a pleasure to hear from you.

At XMOS, after some staff churn, I am the most active on the backend, full time at the moment. I am still learning LLVM and have not yet made an upstream patch, but I am happy to answer questions, run tests, and adapt to new APIs. We also have the silicon team and some institutional memory here, which might be useful in maintaining the backend.

Nigel


From: Chris Lattner <clattner at nondot.org>
Sent: 15 March 2020 19:23
To: Nigel Perks <nigelp at xmos.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] XCore target




On Mar 11, 2020, at 3:03 AM, Nigel Perks via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:


Hello all.

At XMOS we are working towards updating the upstream XCore backend for newer versions of the chip.

XCore is the XMOS processor. The XCore backend was written by Richard Osborne at XMOS. Richard has moved on. The current code owner in CODE_OWNERS.TXT, Robert Lytton, has also moved on.

For some years XMOS has developed the compiler in-house, for new versions of the chip, but not upstreamed the changes. We are currently integrating the upstream changes into the shipping compiler, following the LLVM coding standards. We would like to upstream when possible, but we don't have an estimated date yet.

I hope this sounds promising, and welcome any comments or questions.

Nigel Perks

This all sounds great Nigel.  I think it would also make sense to update the CODE_OWNERS’s file with an active maintainer.  Who do you think is the best candidate?

-Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200316/4057f354/attachment.html>