RE: [PATCHv4, MIPS] Add support for O32 FPXX and program header based ABI information

[Matthew Fortune <Matthew dot Fortune at imgtec dot com>]

Joseph Myers <joseph@codesourcery.com> writes:
> On Wed, 31 Dec 2014, Matthew Fortune wrote:
> 
> > FAIL: conform/ISO/math.h/linknamespace
> 
> I'd expect math.h linknamespace failures only for soft-float (and mips1
> builds, because those use the dbl-64 sqrt implementation which uses
> fegetround).

= conform/ISO/math.h/linknamespace.out =
[initial] __acos -> [libm.a(w_acos.o)] feraiseexcept

> > FAIL: conform/POSIX/fcntl.h/conform
> 
> What are the conform/ failures?  I've never run the conform/ tests for
> MIPS as they're still native-only, but they probably indicate issues in

Out of interest how do you run the testsuite if not natively? I got lots
of failures from qemu user-mode testing especially with nptl tests when I
last tried. N32 'stat*' is also very broken in qemu currently so N32 cross
testing appears impossible until that is resolved.

> MIPS-specific headers (which may or may not be straightforward to fix -
> depends on whether e.g. using POSIX-conforming types for something would
> affect the ABI).

= N64 conform/POSIX/signal.h/conform.out =

  Testing for type of member sa_flags... FAIL
    Member "sa_flags" does not have the correct type.  Compiler message:
    -----------------------------------------------------------------------
    /home/mfortune-test/glibcn64_build/conform/POSIX/signal.h/scratch/signal.h-test.c:4:32: error: conflicting types for 'b'
     extern __typeof__ (a.sa_flags) b;
                                    ^
    /home/mfortune-test/glibcn64_build/conform/POSIX/signal.h/scratch/signal.h-test.c:3:12: note: previous declaration of 'b' was here
     extern int b;
                ^
    -----------------------------------------------------------------------

= N64 conform/POSIX/termios.h/conform =

  Checking the namespace of "termios.h"... FAIL
    ------------------------------------------------------------------------
    Namespace violation: "TIOCSER_TEMT"
    ------------------------------------------------------------------------

= O32 conform/POSIX/fcntl.h/conform =

  Checking the namespace of "fcntl.h"... FAIL
    ------------------------------------------------------------------------
    Namespace violation: "pad"
    ------------------------------------------------------------------------

= O32 conform/POSIX/mqueue.h/conform =

  Checking the namespace of "mqueue.h"... FAIL
    ------------------------------------------------------------------------
    Namespace violation: "pad"
    ------------------------------------------------------------------------

There are also some XPASSes:

(N64/O32/N32 unexpected pass)
XPASS: conform/ISO11/complex.h/conform
XPASS: conform/ISO11/stdalign.h/conform
XPASS: conform/ISO11/stdnoreturn.h/conform

(O32/N32 unexpected pass)
XPASS: conform/POSIX2008/fcntl.h/linknamespace
XPASS: conform/POSIX2008/mqueue.h/linknamespace
XPASS: conform/XOPEN2K/fcntl.h/linknamespace
XPASS: conform/XOPEN2K/mqueue.h/linknamespace
XPASS: conform/XOPEN2K/utmpx.h/conform
XPASS: conform/XOPEN2K8/fcntl.h/linknamespace
XPASS: conform/XOPEN2K8/mqueue.h/linknamespace

> 
> > FAIL: elf/check-abi-libc
> 
> You should not be seeing this (at least, if you configured --
> prefix=/usr)
> - what is the failure?

This is due to using a different prefix so this is not a failure.

> 
> > FAIL: elf/check-execstack
> > FAIL: elf/check-localplt
> > FAIL: elf/tst-audit1
> > FAIL: elf/tst-audit2
> > FAIL: elf/tst-audit8
> > FAIL: elf/tst-audit9
> 
> Expected.
> 
> > FAIL: inet/test-ifaddrs
> > FAIL: inet/test_ifindex
> 
> What are the failures here?  It's odd for these to be architecture-
> specific.

Both of these fail to find any network interfaces even though there are
'lo' and 'mgmt0' listed by ifconfig. I'm running a modified 3.10.20
kernel so it shouldn't be too old though I don't know exactly how it
is modified! If there are no known issues here then I will try and
find out what exactly is failing.

> 
> > FAIL: math/atest-exp2
> > FAIL: math/atest-sincos
> 
> Assuming you have a sufficient TIMEOUTFACTOR you shouldn't see these
> failing.

These are timing out.

> 
> > FAIL: rt/tst-cputimer1
> 
> Known intermittent failure (maybe a kernel issue?).

I guess it must be. I can't guarantee anything but I'll try and remember
to bring it up with our kernel team and see if someone can investigate.

Thanks,
Matthew