https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #15 from Sam James <sjames at gcc dot gnu.org> --- (In reply to David Malcolm from comment #14) > FWIW I tried again building emacs (from git) with gcc trunk with > --with-native-compilation=aot on x86_64 and, annoyingly, "make" completed > successfully; I see lots of > ./native-lisp/31.0.50-677d9325/*.eln > which are "ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), > statically linked, not stripped" > I'll get back to trying to find how to configure GCC s.t. it happens. It seems like in the right environment, it always happens, I just don't know what the condition is yet. > How clean is Emacs under valgrind normally? It's clean "enough" if you... a) pass -DUSE_VALGRIND in CFLAGS or CPPFLAGS when building, and b) use a suppression file (like https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-01/txtaJC0QpICF7.txt, which isn't perfect, but it made the output mostly clean for me) When I ran the crasher under Valgrind, the only output I saw besides GC noise at the beginning was the invalid access on the null deref. I didn't see anything that looked useful or around the time of the crash, and the bit I did see seemed like the usual innocent GC noise for Emacs.
