----- Am 30. Mai 2017 um 22:41 schrieb Hesham Almatary heshamelmat...@gmail.com:
> Hi Sebastian, > > On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber > <sebastian.hu...@embedded-brains.de> wrote: >> Hello Hesham, >> >> thanks for your RISCV support. >> >> ----- Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary >> heshamelmat...@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]. Ok, I checked in your patch. Could you please try to move the RTEMS support into the standard ELF target support, see ARM support for RTEMS as an example. Using the ELF section helps to get updates for free or at least someone asks us before changing things. _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
