btashton opened a new issue #1274: URL: https://github.com/apache/incubator-nuttx/issues/1274
There are a bunch of configurations that are certainly broken in the RISC-V port at least for the rv32im version. There is a bunch of logic that is conditional on the MIPS that looks like was left when ported. ``` src/rv32im/riscv_copystate.c: /* In the MIPS model, the state is copied from the stack to the TCB, src/rv32im/riscv_vfork.c:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.c:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.c:#ifdef MIPS32_SAVE_GP src/rv32im/riscv_vfork.c:#ifdef MIPS32_SAVE_GP src/rv32im/riscv_vfork.c: /* How much of the parent's stack was utilized? The MIPS uses src/rv32im/riscv_vfork.c:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.c:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.c:#ifdef MIPS32_SAVE_GP src/rv32im/riscv_vfork.h:#ifndef __ARCH_MIPS_SRC_MIPS32_VFORK_H src/rv32im/riscv_vfork.h:#define __ARCH_MIPS_SRC_MIPS32_VFORK_H src/rv32im/riscv_vfork.h:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.h:#ifdef MIPS32_SAVE_GP src/rv32im/riscv_vfork.h:#ifdef CONFIG_MIPS32_FRAMEPOINTER src/rv32im/riscv_vfork.h:#ifdef MIPS32_SAVE_GP src/rv32im/riscv_vfork.h:#endif /* __ARCH_MIPS_SRC_MIPS32_VFORK_H */ src/rv32im/riscv_swint.c:#ifdef MIPS32_SAVE_GP src/common/riscv_createstack.c:/* MIPS requires at least a 4-byte stack alignment. For floating point use, src/common/riscv_createstack.c: /* The MIPS stack must be aligned at word (4 byte) boundaries; for src/common/riscv_stackframe.c:/* MIPS requires at least a 4-byte stack alignment. For floating point use, src/common/riscv_usestack.c:/* MIPS requires at least a 4-byte stack alignment. For floating point use, src/common/riscv_usestack.c: /* MIPS uses a push-down stack: the stack grows toward loweraddresses in src/common/riscv_usestack.c: /* The MIPS stack must be aligned at word (4 byte) or double word (8 byte) ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
