[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] RISC-V support
From: |
Christian Jullien |
Subject: |
Re: [Tinycc-devel] RISC-V support |
Date: |
Mon, 2 Sep 2019 06:32:34 +0200 |
Michael,
First of all, I would like to send you huge thanks for your investments in tcc
project.
RISC-V backend is, IMHO a very valuable addition to tcc even if the number of
real hardware is currently low.
I'm very impatient to have access to real board now.
I'll try to contact the few RISC-V vendors to ask them to add one of their
machines to the gnufarm.
The very least thing I can do is to test tcc on machines you don't have access
to and I'm very glad to tell you that my Windows 32/64 backends tcc
reproducible builds still work ROOTB.
As usual, you did a very good job.
May I suggest you to add a copyright/license header for the new files you added
+ section on RELICENSING?
Question, what RISC-V flavor(s) do you support, i.e. what is the minimal RSIC-V
subset do you require? If I've read correctly, RISC-V is a modular architecture
with optional features (hard float, MMU..)
C.
-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=address@hidden] On
Behalf Of Michael Matz
Sent: Monday, September 02, 2019 00:42
To: address@hidden
Subject: [Tinycc-devel] RISC-V support
Hi,
On Fri, 21 Jun 2019, Larry Doolittle wrote:
>> Every compiler has its own benefits. That's why tcc still exists
>> in particular. :)
>
> Right. Wake me when clang can target MSP430 and microblaze.
>
> Adding RISC-V support to tcc would be _extremely_ interesting.
Pushed to mob. Tested on openSUSE and Debian riscv64 distros, but only
via a qemu, not on real hardware. The thing is enough to compile itself
and the full testsuite, so it's reasonably complete (e.g. the fancy
argument passing and long double support is there). No compressed code is
generated, inline asm isn't supported. Given the limitations of the TCC
code generator the quality of the generated code is on par with the other
architectures (i.e. horrible :-) ).
I did my best to test the other targets, but only checked armhf, aarch64,
i386 and x86-64 on linux; i.e. the windows backends weren't checked.
Still, have fun.
Ciao,
Michael.
_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] RISC-V support, Giovanni Mascellani, 2019/09/02