https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94609
--- Comment #11 from Iain Buclaw <ibuclaw at gdcproject dot org> --- (In reply to H.J. Lu from comment #9) > > I tested with glibc 2.30 with fix for > > https://sourceware.org/bugzilla/show_bug.cgi?id=25810 > Nice, though currently the library testsuite is compiled at -O0. I want to turn on -O2 however, which causes many x32 tests to start failing, some with very hard to debug reasons. > I got > > FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos_shared/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos_shared/std/conv.d execution test > FAIL: libphobos.phobos_shared/std/conv.d execution test > FAIL: libphobos.phobos_shared/std/conv.d execution test > FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test > FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test > FAIL: libphobos.phobos_shared/std/datetime/systime.d execution test > FAIL: libphobos.phobos_shared/std/range/primitives.d (test for excess errors) > FAIL: libphobos.phobos/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos/std/algorithm/mutation.d execution test > FAIL: libphobos.phobos/std/conv.d execution test > FAIL: libphobos.phobos/std/conv.d execution test > FAIL: libphobos.phobos/std/conv.d execution test > FAIL: libphobos.phobos/std/datetime/systime.d execution test > FAIL: libphobos.phobos/std/datetime/systime.d execution test > FAIL: libphobos.phobos/std/datetime/systime.d execution test > FAIL: libphobos.phobos/std/range/primitives.d (test for excess errors) > > with > > $ make check RUNTESTFLAGS="--target_board='unix{-mx32,-m32,}'" I've seen this too. If nested structs are to be passed by invisible reference now, we still need copy semantics if there is no defined cpctor or dtor. I'm just thinking about the best location to handle this. Will have something by morning after running it by the testsuite again.
