Jérémy Lal <kapo...@melix.org> 于2022年8月4日周四 18:39写道: > > > > Le jeu. 4 août 2022 à 12:36, Xi Ruoyao <xry...@xry111.site> a écrit : >> >> On Thu, 2022-08-04 at 18:18 +0800, YunQiang Su wrote: >> > > 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)); >> > > >> > >> > @Xi Ruoyao Is this what you are working on? >> >> 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. >
I mean is it about then zero legth var in C++? > > No evidence yet. > Upstream nodejs says it might very well be a bug on their side. > I'll reassign accordingly. > > -- YunQiang Su