This is the mail archive of the gdb-testers@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Sunday Project test results, gdb, 2002-02-16


. Summary

  . Test Matrix

    . Matrix

      target:   native
      host:     i686-pc-linux-gnulibc2.2:rh-7.2
      gdb:      5.1.1, gdb_5_1-2001-07-29-branch:20020216, HEAD:20020216
      gcc:      2.95.3, 3.0.3, 3.0.4-20020215, gcc-3_0-branch:20020216, HEAD:20020216
      goption:  -gdwarf-2, -gstabs+
      count:     30=1*1*3*5*2

    . Notes

      target and host names are gnu triples with extra information after
      a ':' delimiter.

      versions which start with a number are official releases or tarballs.
      versions named HEAD are the cvs HEAD (mainline).
      versions with any other name are cvs branches.
      cvs versions show the date pulled after a ':' delimiter

      gcc release versions are built with binutils 2.11.2.
      gcc CVS versions are built with binutils HEAD from the same date.

  . Aggregate results

    . libiberty

      all tests passed

    . gdb 5.1.1

        0  build failures
	0  test run failures
       21  ERROR
       14  WARNING
      453  FAIL

    . gdb gdb_5_1-2001-07-29-branch

        0  build failures
        0  test run failures
       21  ERROR
       14  WARNING
      452  FAIL

    . gdb HEAD

        0  build failures
	0  test run failures
	3  ERROR
	3  WARNING
      233  FAIL

    . Tables

      http://www.shout.net/~mec/sunday/2002-02-16/index.html

    . Old bugs fixed

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=348
      gdb testsuite programs: "warning: no return statement in function returning non-void"
      Half of this bug was fixed in gdb HEAD.

    . New bugs detected

      None.



. Test protocol changes since last report

  I dropped gdb 5.1.

  I dropped gcc 3.0.2.

  I added gcc 3.0.4-20020215.  I found no regressions versus gcc 3.0.3.
  I found two improvements: gdb.base/break.exp and gdb.base/step-line.exp.
  I filed a separate report to gcc-testresults and gdb-testresults
  (not gdb-testers, oops).

  I attempted to add native i686-pc-cygwin, but the baseline software
  failed to build due to a case problem with "gnu" versus "Gnu" in
  the java libraries.  I will pursue this as a gcc bug, and I will
  seek to build the baseline software without java libraries.

  I considered dropping gdb gdb_5_1-2001-07-29-branch.  I am likely to
  drop this version of gdb at any time.



. Baseline software

  . host i686-pc-linux-gnu:rh-7.2

    make 3.79.1
    binutils 2.11.2
    gcc 3.0.3
    tcl 8.3.4
    expect 5.33.0
    dejagnu 1.4.2



. Analysis

  . libiberty

    . results

      . target i686-pc-linux-gnulibc2.2-rh7.2

        . host native

          binutils HEAD                         All 647 tests passed
          gcc gcc-3_0-branch                    All 646 tests passed
          gcc HEAD                              All 647 tests passed
          gdb gdb_5_1-2001-07-29-branch         All 645 tests passed
          gdb HEAD                              All 647 tests failed

    . commentary

      It appears that gcc gcc-3_0-branch and gdb gdb_5_1-2001-07-29-branch
      have older versions of libiberty.  That is okay.

  . gdb

    The last report was 2002-02-09.

    . 5.1.1

      . Regressions

	None.

      . Improvements

	None.

    . gdb_5_1-2001-07-29-branch

      . Regressions

	None.

      . Improvements

	None.

    . HEAD

      . Regressions

	None.

      . Improvements

	gdb.base/funcargs.exp with gcc HEAD: part of PR gdb/348 was fixed.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]