LLVM status request

Reinoud Zandijk

unread,

Aug 12, 2016, 10:01:52 AM8/12/16

to sw-...@groups.riscv.org

Dear folks,

what is the current status of LLVM? Is it in a state to completely replace gcc
i.e. without dependencies on it? How about the commonly used libraries, are
they also compilable with only LLVM installed?

With regards,
Reinoud

John Leidel

unread,

Aug 12, 2016, 10:05:27 AM8/12/16

to Reinoud Zandijk, RISC-V SW Dev

Reinoud, not yet. The object generation isn't quite complete and there are a number of things in the codegen that can likely be improved. We also lack support in LLD and LLDB. Our group is currently working on both. I haven't looked at the libc++ support, but I suspect this won't be terrible. At one point, we had an (LLVM) OpenMP implementation ported, but it desperately needs to be re-written (too many changes since we did it).

--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.
To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/20160812140147.GA8894%40nas.13thmonkey.org.

James Y Knight

unread,

Aug 12, 2016, 10:20:49 AM8/12/16

to John Leidel, Reinoud Zandijk, RISC-V SW Dev

Is someone working on preparing the existing code to send for upstream review?

I think the community would be much better served at this point by doing further development on the llvm risc-v port in llvm upstream, rather than in a separate branch.

On Fri, Aug 12, 2016 at 10:05 AM, John Leidel <john....@gmail.com> wrote:

Reinoud, not yet. The object generation isn't quite complete and there are a number of things in the codegen that can likely be improved. We also lack support in LLD and LLDB. Our group is currently working on both. I haven't looked at the libc++ support, but I suspect this won't be terrible. At one point, we had an (LLVM) OpenMP implementation ported, but it desperately needs to be re-written (too many changes since we did it).

On Fri, Aug 12, 2016 at 9:01 AM, Reinoud Zandijk <rei...@netbsd.org> wrote:

Dear folks,

what is the current status of LLVM? Is it in a state to completely replace gcc
i.e. without dependencies on it? How about the commonly used libraries, are
they also compilable with only LLVM installed?

With regards,
Reinoud

--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.

To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/20160812140147.GA8894%40nas.13thmonkey.org.

--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+unsubscribe@groups.riscv.org.
To post to this group, send email to sw-...@groups.riscv.org.
Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CAC6GRO8nW%3DGGeyD-AHrEeU%3D8-21Dppv%3Dw933yPGM17M%2B72PMng%40mail.gmail.com.

Alex Bradbury

unread,

Aug 12, 2016, 4:06:33 PM8/12/16

to James Y Knight, John Leidel, Reinoud Zandijk, RISC-V SW Dev

I have a bunch of patches I'll try to get sent out early next week. I was going to get it sent out today but something came up.

Alex

On Friday, 12 August 2016, 'James Y Knight' via RISC-V SW Dev <sw-...@groups.riscv.org> wrote:
> Is someone working on preparing the existing code to send for upstream review?
> I think the community would be much better served at this point by doing further development on the llvm risc-v port in llvm upstream, rather than in a separate branch.
> On Fri, Aug 12, 2016 at 10:05 AM, John Leidel <john....@gmail.com> wrote:
>>
>> Reinoud, not yet. The object generation isn't quite complete and there are a number of things in the codegen that can likely be improved. We also lack support in LLD and LLDB. Our group is currently working on both. I haven't looked at the libc++ support, but I suspect this won't be terrible. At one point, we had an (LLVM) OpenMP implementation ported, but it desperately needs to be re-written (too many changes since we did it).
>> On Fri, Aug 12, 2016 at 9:01 AM, Reinoud Zandijk <rei...@netbsd.org> wrote:
>>>
>>> Dear folks,
>>>
>>> what is the current status of LLVM? Is it in a state to completely replace gcc
>>> i.e. without dependencies on it? How about the commonly used libraries, are
>>> they also compilable with only LLVM installed?
>>>
>>> With regards,
>>> Reinoud
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
>>> To post to this group, send email to sw-...@groups.riscv.org.
>>> Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.
>>> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/20160812140147.GA8894%40nas.13thmonkey.org.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
>> To post to this group, send email to sw-...@groups.riscv.org.
>> Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

>> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CAC6GRO8nW%3DGGeyD-AHrEeU%3D8-21Dppv%3Dw933yPGM17M%2B72PMng%40mail.gmail.com.

>
> --
> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
> To post to this group, send email to sw-...@groups.riscv.org.
> Visit this group at https://groups.google.com/a/groups.riscv.org/group/sw-dev/.

> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CAA2zVHoOQnNawpWSoCNsP174Vte6dBa1UNcGHgXHak%3D4MsGVVg%40mail.gmail.com.
>

Alex Bradbury

unread,

Aug 17, 2016, 10:06:47 AM8/17/16

to RISC-V SW Dev, John Leidel, Reinoud Zandijk

On 12 August 2016 at 21:06, Alex Bradbury <a...@asbradbury.org> wrote:
> I have a bunch of patches I'll try to get sent out early next week. I was
> going to get it sent out today but something came up.

As a follow-up to this, please see my RFC on the LLVM mailing list
http://lists.llvm.org/pipermail/llvm-dev/2016-August/103748.html and
my initial patch set
https://reviews.llvm.org/differential/?authors=asb

Best,

Alex

Arun Thomas

unread,

Aug 17, 2016, 12:05:11 PM8/17/16

to Alex Bradbury, RISC-V SW Dev, John Leidel, Reinoud Zandijk

Great work, Alex. The responses on the LLVM mailing list are very encouraging.

I'm looking forward to having LLVM/RISC-V on FreeBSD.

Arun

John Leidel

unread,

Aug 17, 2016, 1:45:02 PM8/17/16

to Alex Bradbury, RISC-V SW Dev, Reinoud Zandijk

Alex, this is great news. I'm going to jump Phabricator and start reviewing...

cheers

john

Kito Cheng

unread,

Nov 1, 2016, 8:51:24 AM11/1/16

to RISC-V SW Dev, a...@asbradbury.org, rei...@netbsd.org, col...@eecs.berkeley.edu, Andrew Waterman

Hi all:

Any update status for LLVM?

Alex's one seem no update since mid-october, and Foundation's last update is 3 month ago.

Any plan for merge both version? or Alex's one will replace Foundation's port?

Alex Bradbury

unread,

Nov 1, 2016, 9:25:40 AM11/1/16

to Kito Cheng, RISC-V SW Dev, Reinoud Zandijk, Colin Schmidt, Andrew Waterman

On 1 November 2016 at 12:51, Kito Cheng <npic...@gmail.com> wrote:
> Hi all:
>
> Any update status for LLVM?
> Alex's one seem no update since mid-october, and Foundation's last update is
> 3 month ago.

I'm presenting a short lightning talk on the RISC-V LLVM port at the
LLVM Dev Meeting on Thu. The initial set of patches are ready for
merging, which will happen any day now, and I'm almost ready to put
the next series up for review.

Best,

Alex

Colin Schmidt

unread,

Nov 1, 2016, 1:12:43 PM11/1/16

to Alex Bradbury, Kito Cheng, RISC-V SW Dev, Reinoud Zandijk, Andrew Waterman

I think Alex's should replace the riscv/riscv-llvm port once its upstreamed. Then all RISC-V + LLVM people can contribute to fixing issues/improving functionality (hopefully) more easily.

The old one will be kept around for posterity(as most old repos are) for some time, with a clear deprecated warning.

Kito Cheng

unread,

Nov 1, 2016, 10:47:04 PM11/1/16

to Colin Schmidt, Alex Bradbury, RISC-V SW Dev, Reinoud Zandijk, Andrew Waterman

Hi Alex:

Would you like to put your port into riscv/riscv-llvm or lowRISC/riscv-llvm repo since I think there are many people interest for that and as Colin say we can fixing/improving that just like current GNU toolchain development for RISC-V in github :)

David Chisnall

unread,

Nov 2, 2016, 5:36:56 AM11/2/16

to Kito Cheng, Colin Schmidt, Alex Bradbury, RISC-V SW Dev, Reinoud Zandijk, Andrew Waterman

On 2 Nov 2016, at 02:46, Kito Cheng <npic...@gmail.com> wrote:
>
> Hi Alex:
>
> Would you like to put your port into riscv/riscv-llvm or lowRISC/riscv-llvm repo since I think there are many people interest for that and as Colin say we can fixing/improving that just like current GNU toolchain development for RISC-V in github :)

Alex’s work is in the LLVM tree:

http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/RISCV/

If anyone wants to work on it, I’d suggest forking the LLVM repo on GitHub and submitting patches via LLVM’s Phabricator instance (https://reviews.llvm.org). Working out of tree is largely counterproductive - the larger the out-of-tree changes get without upstream review, the harder it is to upstream them. Small incremental patches are easy to review and commit. Take a look in Phabricator for the patches that Alex already had reviewed - they were very easy for me and others to inspect and serve as a good example of how to work with an upstream project.

David

Kito Cheng

unread,

Nov 2, 2016, 12:48:09 PM11/2/16

to David Chisnall, Colin Schmidt, Alex Bradbury, RISC-V SW Dev, Reinoud Zandijk, Andrew Waterman

Hi David:

I've seem Alex's patch in Phabricator, and I agree your point for working upstream :)

btw I am curious about the status for the Alex's port, I mean the other part: clang and SelectionDAG, does it include in next series?

Reply all

Reply to author

Forward