On Wed, 16 Dec 2020, Al Viro wrote: > > It may be worth pushing through GDB's gdb.threads/tls-core.exp test case, > > making sure no UNSUPPORTED results have been produced due to resource > > limits preventing a core from being dumped (and no FAILs, of course), with > > o32/n32 native GDB. This should guarantee our output is still as expected > > by an interpreter. Sadly I'm currently not set up for such testing though > > eventually I mean to. > > Umm... What triple does one use for n32 gdb? I don't think there's a standardised one, just configure with CC/CXX set for n32 compilation, e.g.: $ /path/to/configure CC="gcc -mabi=n32" CXX="g++ -mabi=n32" (and any other options set as usually). This has to be with CC/CXX rather than CFLAGS/CXXFLAGS so that it is guaranteed to be never overridden with any logic that might do any fiddling with compilation options. This will set up the test suite accordingly. NB this may already be the compiler's default, depending on how it was configured, i.e. if `--with-abi=n32' was used, in which case no extra options will be required. I don't know if any standard MIPS distribution does it though; 64-bit MIPS/Debian might. This will be reported with `gcc --help -v', somewhere along the way. Let me know if there are issues with this approach. Maciej
