[PATCH] Add support to build riscv32 toolchain

[Hesham Almatary]

Hi Sebastian,

On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
> Hello Hesham,
>
> thanks for your RISCV support.
>
> ----- Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary heshamelmatary at gmail.com:
>
>> ---
>> rtems/config/4.12/rtems-riscv32.bset               | 32 +++++++++++
>> rtems/config/tools/rtems-binutils-2.28-1.cfg       | 22 ++++++++
>> .../rtems-gcc-7.1.0-newlib-2.5.0.20170323-1.cfg    | 65 ++++++++++++++++++++++
> [...]
>> +#
>> +# Patches for gcc and newlib
>> +#
>> +%patch add gcc -p1
>> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/gcc-rtems-riscv.patch
>
> Do you have a copyright assignment with the FSF? If not and you don't want to do this, then I can try to add the RISCV support to GCC without locking at your GCC patches. We should commit the things first into GCC.
I do, just need to update my employment status, already talked to FSF
people. Also, this should be merged part of the next gcc-riscv release
[1].

[1] https://github.com/riscv/riscv-gcc/commit/443291274e05821a3425576d5393f3c776069cab
>
>> +%patch add newlib -p1
>> https://raw.githubusercontent.com/heshamelmatary/riscv-rtems-patches/master/0001-Import-risc-v-from-https-github.com-riscv.patch
>
> Are there plans by the RISCV people to add this to upstream Newlib soon? Due to the RISCV support in FSF Binutils and GCC, there should be no problems.
I've asked about that, don't have an answer yet

-- 
Hesham