https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83413
Alexander Perfeito <perfeitoan at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |NVidia ARM Tegra TK1
| |Chromebook
Known to work| |3.4.6, 4.1.2, 4.2.1, 4.6.1
URL| |www.mame.org
Keywords| |wrong-code
Component|other |c++
Host| |NVidia ARM Tegra TK1
| |Chromebook
Known to fail| |7.2.1
Build| |Using built-in specs.
| |COLLECT_GCC=gcc
| |COLLECT_LTO_WRAPPER=/usr/li
| |b/gcc/armv7l-unknown-linux-
| |gnueabihf/7.2.1/lto-wrapper
| |Target:
| |armv7l-unknown-linux-gnueab
| |ihf Configured with:
| |/build/gcc/src/gcc/configur
| |e --prefix=/usr
| |--libdir=/usr/lib
| |--libexecdir=/usr/
--- Comment #1 from Alexander Perfeito <perfeitoan at hotmail dot com> ---
rb6502 commented 22 hours ago •
Sorry, but that's a compiler bug, not something we can address. MAME is known
to be buildable for other ARM targets (e.g. Raspberry Pi) right now so it
appears to be an issue with whatever you're building for.
https://github.com/mamedev/mame/issues/2925
