[PATCH] Add support to build riscv32 toolchain

[Hesham Almatary]

On Wed, May 31, 2017 at 1:21 AM, Gedare Bloom <gedare at rtems.org> wrote:
> Unrelatedly to the contents, please use -v2 to identify revised patches.
>
Yes please ignore the first patch, thanks for the reminder.

> On Tue, May 30, 2017 at 2:01 AM, 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.
>>
>>> +%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.
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel



-- 
Hesham