[PATCH 1/4] cpukit: RISC-V - make riscv32 code work for riscv64

Chris Johns chrisj at rtems.org
Mon Oct 30 04:48:57 UTC 2017

On 29/10/2017 16:59, Hesham Almatary wrote:
> On Fri, Oct 27, 2017 at 8:49 PM, Hesham Almatary
> <heshamelmatary at gmail.com> wrote:
>> * Use #ifdefs for 32/64 bit code
>> * Use unsigned long which is 32-bit on riscv32 and 64-bit on riscv64 (register size)
>> * Move the code to a new shared riscv folder to be shared with riscv64
>> * Symlink riscv -> riscv32
>> * Symlink riscv -> riscv64
> I am wondering if the main idea of sharing (speicifcally having sym
> links) riscv code between riscv32 and riscv64 is fine.

Symlinks are not portable across host operating systems, ie Windows. We should
avoid them.

Shared code can be placed in libcpu. Is this a viable option?


More information about the devel mailing list