Hi, If nodejs 18.6.0 is built using gcc-12, several tests fail, but not when built using gcc-11 (all other things being equal). *Only* on mips64el and riscv64. In the logs, some new warnings show up, maybe that can help: https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=mips64el&ver=18.6.0%2Bdfsg-4&stamp=1659454899&raw=0 in particular: /usr/include/c++/12/bits/atomic_base.h:488:31: warning: ‘long unsigned int __atomic_load_8(const volatile void*, int)’ writing 8 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=] 488 | return __atomic_load_n(&_M_i, int(__m)); Jérémy
Jérémy Lal <kapouer@melix.org> 于2022年8月4日周四 15:12写道: @Xi Ruoyao Is this what you are working on?
Le jeu. 4 août 2022 à 12:36, Xi Ruoyao <xry111@xry111.site> a écrit : No evidence yet. Upstream nodejs says it might very well be a bug on their side. I'll reassign accordingly.
If we have evidence showing it's a GCC code generation bug, I'll try to fix it. I don't have any interest in node.js.
Jérémy Lal <kapouer@melix.org> 于2022年8月4日周四 18:39写道: I mean is it about then zero legth var in C++?
I don't think they are related. "writing x bytes into a region of size 0" is a common false warning with GCC 12. There are multiple PRs about it and I think this is likely https://gcc.gnu.org/PR104475.