3 ms·
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02044.html https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02044.html https://www.phoronix.com/scan.php?page=news_i
by Twirrim 7y ago
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02044.html https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02044.html
https://www.phoronix.com/scan.php?page=news_item&px=GCC-11-m68k-Is-Safe https://www.phoronix.com/scan.php?page=news_item&px=GCC-11-m...
There are some back-end changes coming to GCC, and no one had ported m68k to it (presumably there is no maintainer for m68k in GCC?) The back-end code the m68k code was relying upon was going away, and it needed ported to use the modern one. Someone has stepped up and done that work, so it gets to live another day.
https://gcc.gnu.org/backends.html https://gcc.gnu.org/backends.html based on this is looks like avr, cris, h8300, mn10300 and vax are yet to be ported away from cc0.