On Mon, 11 Dec 2023, Jeff Law wrote: > > This happened with the late-combine pass that I posted in October: > > https://gcc.gnu.org/pipermail/gcc-patches/2023-October/634166.html > > which in turn triggered an error from aarch64_print_operand_address. > > > > This patch takes the (hopefully) conservative fix of using VOIDmode for > > asms but continuing to use the operand mode for .md insns, so as not > > to break ports that still use reload. > Sadly I didn't get as far as I would have liked in removing reload, though we > did get a handful of ports converted this cycle
The VAX port isn't ready for LRA yet as not only LRA produces notably worse RISC-like code ignoring all the architecture's address mode features (unenthusiatically acceptable), but it causes testsuite regressions of the ICE kind (unacceptable) as well. I did hope to at least start work on it in this release cycle, but there has been this outstanding issue of broken exception unwinding, which makes C++ unusuable except for odd cases such as with GCC itself where exceptions are not used. This unwinder issue obviously has to take precedence as it cripples the usability of code produced by the compiler even for developer's use, e.g. native VAX/GDB is mostly broken and even VAX/gdbserver quits with a crash. I can try and see if I can find some time over the festive period to move the VAX port forward in either respect. Maciej
