On Thu, Jun 14, 2018 at 11:59 AM, Sebastian Huber
wrote:
> The change in config.gcc could break all RISC-V ports, e.g. some typo leading
> to a syntax error. I would like to back port this to GCC 7 and 8.
The backports are OK with me. Though I think you will need permission
from the branch main
- Am 14. Jun 2018 um 20:23 schrieb Jim Wilson j...@sifive.com:
> On Wed, Jun 13, 2018 at 9:57 PM, Sebastian Huber
> wrote:
>> gcc/
>> * config.gcc (riscv*-*-elf* | riscv*-*-rtems*): Use custom
>> multilibs for *-*-rtems*.
>> * config/riscv/t-rtems: New file.
>
> Loo
On Wed, Jun 13, 2018 at 9:57 PM, Sebastian Huber
wrote:
> gcc/
> * config.gcc (riscv*-*-elf* | riscv*-*-rtems*): Use custom
> multilibs for *-*-rtems*.
> * config/riscv/t-rtems: New file.
Looks OK to me. Though I think you can probably self approve patches
like this that
Add multilib variants for -march=rv64imafd, e.g. to support the BOOMv2 core.
Add -mcmodel=medany as a variant of the 64-bit multilibs for RTEMS. The
ratinale for this change is that several existing RISC-V chips map the
RAM at 0x8000. In RTEMS, we do not use virtual memory, so
applications w