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-03-02


This was a quiet half-week.  There was one bug fix in gdb plus one
improvement in gcc that improves the gdb 5.1.1 test results.  No new
gdb bugs or gdb test suite regressions manifested.

Michael C

===

. Summary

  . Test Matrix

    . Matrix

      target:   native
      host:     i686-pc-linux-gnulibc2.2%rh-7.2
      gdb:      5.1.1, HEAD%20020302
      gcc:      2.95.3, 3.0.4, gcc-3_1-branch%20020302, HEAD%20020302, vendor
      glibc:    vendor
      goption:  -gdwarf-2, -gstabs+
      count:    20=1*1*2*5*1*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 snapshots.
      versions named "vendor" are the vendor-supplied facility.
      versions named "HEAD" are the cvs HEAD (mainline).
      versions with any other name are cvs branches.
      cvs versions show the pull date after a '%' delimiter.

      gcc releases and snapshots are built with binutils 2.11.2

      gcc cvs versions are built with binutils HEAD%20020226.
      usually I use binutils HEAD with the same pull date,
      but binutils HEAD%20020302 builds a bad ld:

        /berman/fsf/_today_/berman/native/install/binutils/HEAD/bin/ld:built in linker script:49: parse error

      I probably just picked a bad time to pull binutils HEAD.
      If the problem persists then I will pursue it on the binutils lists.

  . libiberty

    all tests passed

  . gdb

    . Tables

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

    . Overview

      gdb 5.1.1: 0 build failures, 0 test run failures, 400 attention lines
      gdb HEAD:  0 build failures, 0 test run failures, 339 attention lines

      an attention line is:
        error warning fail kfail unresolved untested unsupported
      an attention line is not:
        pass xpass xfail

    . Old bugs fixed

      In gcc v3 -gstabs+ configurations, a name mangling bug regarding
      static functions was fixed.

      http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr5725
      "no return statement in function returning non-void" on legal pthread style code
      this was a gcc issue which impacted some gdb 5.1.1 test suite programs

    . New bugs detected.

      None.

. Test protocol changes since last report

  I added vendor gcc to the compilers under test.  This is the version
  of gcc that comes with the host system.

. Baseline software

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

    make 3.79.1
    binutils 2.11.2
    gcc 3.0.4
    flex 2.5.4
    bison 1.33
    tcl 8.3.4
    expect 5.33.0
    dejagnu 1.4.2

. Analysis

  . libiberty

    . results

      . target native

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

          binutils HEAD                         All 648 tests passed
          gcc gcc-3_1-branch                    All 648 tests passed
          gcc HEAD                              All 648 tests passed
          gdb HEAD                              All 648 tests passed

  . gdb

    The last report was 2002-02-26.

      http://www.shout.net/~mec/sunday/2002-02-26/Analysis.txt

    . 5.1.1

      . Difference Grid

        gdb.base/funcargs.exp           ,5 ,6 ,7 ,8
        gdb.base/linux-dp.exp           ,5 ,6 ,7 ,8
        gdb.base/pthreads.exp           ,5 ,6 ,7 ,8

        Column numbers are configuration numbers in:

          http://www.shout.net/~mec/sunday/2002-03-02/Differences-compare-by-date-two.html

        + gdb improved
        - gdb regressed
        * new test with good result
        _ new test with bad result
        , noise: result changed but gdb behavior did not

      . Noise

        . gdb.base/funcargs.exp
          gdb.base/linux-dp.exp
          gdb.base/pthreads.exp

          gcc fixed the warning "warning: no return statement in function
          returning non-void", which was overly aggressive and causing
          test suite compilation fails.

    . HEAD

      . Difference Grid

        gdb.c++/annota2.exp             ,12 ,13
        gdb.c++/classes.exp             +12     +14     +16
        gdb.c++/virtfunc.exp            +12     +14     +16

        Column numbers are configuration numbers in:

          http://www.shout.net/~mec/sunday/2002-03-02/Differences-compare-by-date-two.html

        + gdb improved
        - gdb regressed
        * new test with good result
        _ new test with bad result
        , noise: result changed but gdb behavior did not

      . Gdb Improved

	. gdb.c++/classes.exp
	  gdb.c++/virtfunc.exp

	  In gcc v3 -gstabs+ configurations, a name mangling bug regarding
	  static functions was fixed.

      . Noise

	. gdb.c++/annota2.exp

	  This test is not stable.


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