Hi,

QEMU is fast enough for development (that's how I did the AArch32, AArch64, and MIPS bring-up for libobjc2). I haven't written the assembly code paths for RISC-V because I don't have sufficient time + interest. I'm happy to review patches.

If I have time, I'd like to refactor the existing objc_msgSend code into a set of platform-specific macros and a generic implementation, which should make porting to new architectures a bit easier.

David

On 07/10/2021 17:46, lars.sonchocky-helld...@hamburg.de wrote:
Hi fellow GNUsteppers,


I am thinking about purchasing a HiFive Unmatched https://www.sifive.com/boards/hifive-unmatched <https://www.sifive.com/boards/hifive-unmatched> board for helping to port GNUstep and especially the GNUstep ObjC runtime to RISC-V.

But first I would need to know if there is interest in porting GNUstep to RISC-V.

If so, I would buy such a board and connect it to the network with ssh access for those doing the porting. Sorry for doing it this way, I am just not fit enough to port things like https://github.com/gnustep/libobjc2 <https://github.com/gnustep/libobjc2> on my own.

Please reply if you have the skills to help porting GNUstep and want to help porting GNUstep to RISC-V.


kind regards,

Lars

Reply via email to