[Bug other/11411] New: libffi testing problems

["gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11411

           Summary: libffi testing problems
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ro at techfak dot uni-bielefeld dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc-sun-solaris2.8
  GCC host triplet: sparc-sun-solaris2.8
GCC target triplet: sparc-sun-solaris2.8

Although libffi has a separate test program (libffi), this isn't currently
run during make check.  It has to be invoked manually (and may even need to
set LD_LIBRARY_PATH so libgcc_s.so is found at runtime).  This is
inconvenient and can easily lead to overlooking bugs in libffi.

Environment:
System: SunOS tikal 5.8 Generic_108528-19 sun4u sparc SUNW,Sun-Blade-1000
Architecture: sun4

	
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: /vol/gnu/src/gcc/gcc-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls

How-To-Repeat:
Run make check in libffi.
------- Additional Comments From ro at techfak dot uni-bielefeld dot de  2003-07-02 18:29 -------
Fix:
Even if ffitest were run by make check, the output can easily be overlooked
in the output of a whole make check run.  To fix this, ffitest should be
integrated into the dejagenu framework so test results show up in the
testsuite report.

Even better, instead of having a single monolithic test (which can only
produce a single PASS or FAIL result), ffitest should be split into several
independant tests to get a better overview of libffi functionality/problems.