"zifencei" extension?

[vindicator]

I've been toying with Zephyr a little bit, while adapting it to use the esp-idf master branch, and I'm now at the stage where it fails with:

Code: Select all

Fatal error: -march=rv32ima_zicsr_zifencei: Invalid or unknown z ISA extension: 'zifencei'

And I see the flags

Code: Select all

-mabi=ilp32 -march=rv32ima_zicsr_zifencei

I came across https://github.com/zephyrproject-rtos/z ... 1225697737 and https://github.com/zephyrproject-rtos/z ... 1f1a56#top

I don't know if that extension is applicable to the C3, or how to incorporate it with your crosstool-ng.

EDIT0: I just noticed the "rv32ima" part when I was looking at the meanings at https://en.wikipedia.org/wiki/RISC-V.
I've only ever known it to be "rv32imc" based on https://docs.espressif.com/projects/esp ... about.html, along with the esp-idf build output like "riscv32-esp-elf/bin/../lib/gcc/riscv32-esp-elf/11.2.0/../../../../riscv32-esp-elf/lib/rv32imc/ilp32/no-rtti/"

EDIT1: Looking at the project a little more, it seems to be lacking on feaures for devices. The first thing that stood out to me was the dtsi register value for tnrg which did not even remotely resemble what's in the datasheet (24.5 Register Summary).
Then it doesn't even take advantage of the crypto hardware acceleration.
While I could make my own dts with the correct "espressif,esp32-trng" register, it doesn't look like I can do that for any of the crypto features, given there is no associated "compatible" "vendor,device".
I respect/admire zephyr's ambition for unity, but these issues just make it dead-in-the-water for me. Best to just stick with each vendor's SDK.