Zcmt issues with latest binutils build
silabs-hfegran opened this issue · 1 comments
Two issues:
- Index boundaries between cm.jt and cm.jalt should be at 32, not 64 (glancing at the code it looks like it should be fixed, but I am still seing errors), cm.jalt is flagged as an error with index inside [32:63]
- The spec specifies that a cm.jt with index suitable for cm.jalt should be decoded as cm.jalt and vice versa; This is currently not possible to do with the current assembler implementation, an error is flagged if one uses an index for the other jump instruction. Should this be illegal from an asm standpoint?
Latest build of binutils (20230220):
The following sources were used in this build:
binutils-gdb: 457bde5 (https://github.com/openhwgroup/corev-binutils-gdb.git)
build-scripts: f838fc127e015bf4d755e6796098903947b3c89e (https://github.com/embecosm/embecosm-toolchain-releases.git)
gcc: 0976f97e333d9abfe666dfe81f5b8d3fcb85a1c6 (https://github.com/openhwgroup/corev-gcc.git)
newlib: f0417a620182083fa787eea90e2e1d9884c8e573 (https://mirrors.git.embecosm.com/mirrors/newlib-cygwin.git)
binutils-gdb-sim: 18ea42a432d16db09fbed5bc9e60b4e3b7c2caa7 (https://github.com/embecosm/riscv-binutils-gdb.git)
I am seeing these error messages in my log when trying to compile assembly code:
This appears to have been resolved with the latest build, thanks!