aswaterman
commented
4 years ago I don’t have time to set this up, but it makes sense.
We’d want a release script that builds several variants (RV32 and RV64; IMAC and GC). We can probably make the GCV and GC variants the same, since we do not plan to support emulation of missing vector features.
On Fri, Feb 7, 2020 at 10:46 AM Georg Sauthoff notifications@github.com wrote:
For getting started with Spike it would be useful to have binary releases of PK under https://github.com/riscv/riscv-pk/releases.
Usecase: One already has the RISC-V Binutils and Spike installed. With a binary PK release one could immediately test some user-space assembly code in Spike, i.e. without having to compile a full RISC-V GNU toolchain that is required to compile the PK.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/riscv/riscv-pk/issues/189?email_source=notifications&email_token=AAH3XQRVSX3V7DEVZDGRASDRBWUALA5CNFSM4KRTEIK2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IL4QOMQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAH3XQWPXFAVBUYBEQ3FTATRBWUALANCNFSM4KRTEIKQ .
czhaneva
For getting started with Spike it would be useful to have binary releases of PK under https://github.com/riscv/riscv-pk/releases.
Usecase: One already has the RISC-V Binutils and Spike installed. With a binary PK release one could immediately test some user-space assembly code in Spike, i.e. without having to compile a full RISC-V GNU toolchain that is required to compile the PK.