-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are P* extensions supported ? #1291
Comments
I'm not sure if anything has changed since this? |
Not supported, this repo are using upstream GNU toolchain source tree, and upstream GNU toolchain not supported yet since it never get ratified, but you could use external GCC and binutils source tree from PLCT or Andes https://github.com/andestech/gcc. |
In case it helps this worked for me:
And I was able to compile and disassemble the simple example code here: |
Closing the issue since P extension support will be available when (a) the specification is ratified and (b) support is upstreamed to the master GCC and binutils projects. |
Hi, test.s, test.i, test.o are generated but not the output file "Test" I am able to see objdump showing all the P-ext instructions. :: riscv64-unknown-elf-objdump -d test.o Why I am getting below warnings and why output file is not generated? I am seeing below warnings on compilation. /home/manjub/work/riscv_install/riscvtools/lib/gcc/riscv64-unknown-elf/10.2.0/../../../../riscv64-unknown-elf/bin/ld: warning: /home/manjub/work/riscv_install/riscvtools/lib/gcc/riscv64-unknown-elf/10.2.0/../../../../riscv64-unknown-elf/lib/libc.a(lib_a-errno.o): mis-matched ISA version 2.0 for 'f' extension, the output version is 2.2 |
Please clarify and provide...
|
My sincere apologies. Test output is generated, "ll" command was not listing it. Please suggest me how to add "zpn" to spike? |
Do you mean that your previous post can be ignored after all?
I suspect that Spike only supports ratified extensions. I don't know if the PLCT fork of Spike might support If not and there is no other Spike fork that implements |
yes, my post wrt output not generated can be ignored. |
You'll have to ask about this and why your attempt to use it fails over at the Spike and/or P extension pages:
Sorry - I've no idea myself. |
Looks to me like How exactly did you build it? |
Looks like you need to do this:
Enabling the This is the relevant Spike code:
|
Thanks, with "--isa" option I could get spike recognizing the "zpn" sub-ext. git clone https://github.com/plctlab/riscv-gcc -b riscv-gcc-p-ext riscv-gcc-p-ext |
How? You said earlier that you got this:
Yes - as I said here, if you use |
I used to get error on running below command without --isa option:: spike pk Test --- error |
Yes, that's basically what I said above:
|
I am getting below error ::
Assembler messages:
Error: cannot find default versions of the ISA extension
p' /tmp/ccKNSLNd.s:3: Error: cannot find default versions of the ISA extension
p'I have used below build commands::
./configure --prefix=$RISCV --with-arch=rv32gp --with-abi=ilp32
make
The text was updated successfully, but these errors were encountered: