This is the mail archive of the gcc-testresults@gcc.gnu.org mailing list for the GCC 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]

gdb, native i686-pc-linux-gnu


. Highlights of This Spin

  gdb and the gdb test suite had four regressions.

  gcc had no regressions or improvements.

  binutils had no regressions or improvements.

  I added binutils 2.14.92.  The results were substantially the same as
  for binutils 2.14.91, except for gdb.threads/manythreads.exp and
  gdb.threads/print-threads.exp.  manythreads.exp reported some bad
  results which I have not analyzed.  print-threads.exp is currently
  unusable; see pr gdb/1636.

  My current tables are always at

    http://www.shout.net/~mec/sunday/current/index.html

. Gdb Regression Summary

  gdb drow_intercu-20040221-branch versus gdb HEAD
    gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
    gdb.base/call-sc.exp: return foo; return call-sc-tld
    gdb.base/call-sc.exp: value foo returned; return call-sc-td
    gdb.base/call-sc.exp: value foo returned; return call-sc-tf
    gdb.base/call-sc.exp: value foo returned; return call-sc-tld

  gdb HEAD versus gdb 6.1
    gdb/1444 gdb/1613 gdb/1650

  gdb gdb_6_1-branch versus gdb 6.1
    no improvements and no regressions

. Gcc Regression Summary

  gcc tree-ssa-20020619-branch versus gcc HEAD
    gcc/14048 gcc/14049

  gcc HEAD versus gcc 3.4.0
    gcc/13974 gcc/14860

  gcc gcc-3_4-branch versus gcc 3.4.0
    no improvements and no regressions

  gcc 3.4.0 versus gcc 3.3.3
    gcc/12267 gcc/13708 gcc/13956
    gdb/1537 gdb/1540

  gcc gcc-3_3-branch versus gcc 3.3.3
    no improvements and no regressions

  gcc 3.3.3 versus gcc 2.95.3
    not analyzed

. Binutils Regression Summary

  binutils HEAD versus binutils 2.14
  binutils binutils-2_15-branch versus binutils 2.14
  binutils 2.14.92 versus binutils 2.14
  binutils 2.14.91 versus binutils 2.14
    gdb/1470
      gdb no longer has PLT entries for shared library functions
      gdb asks if the user wants to set a pending breakpoint
      the test script shlib-call.exp needs an update
      binutils is okay

. Old Bugs Fixed Since Last Spin

  None.

. New Bugs Detected Since Last Spin

  . gdb gdb_6_1-branch

    http://sources.redhat.com/gdb/bugs/1648
    version.in corrupted on gdb_6_1-branch
 
  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1444
    Return-value struct convention doesn't work with finish or return

    http://sources.redhat.com/gdb/bugs/1650
    manythreads.exp

  . suite HEAD

    http://sources.redhat.com/gdb/bugs/1647
    gdb.base/auxv.exp, incomplete input consumption

. PR Count

  Query executed 2004-05-14 14:28:50 UTC

  1646 matches found
    21 analyzed
   761 closed
    24 feedback
   819 open
     3 paperwork
    18 suspended
  1646 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils binutils-2_15-branch     742 tests, 0 failures
      binutils HEAD                     745 tests, 0 failures
      gcc gcc-3_3-branch                649 tests, 0 failures
      gcc gcc-3_4-branch                745 tests, 0 failures
      gcc HEAD                          745 tests, 0 failures
      gcc tree-ssa-20020619-branch      745 tests, 0 failures
      gdb HEAD                          745 tests, 0 failures
      gdb drow_intercu-20040221-branch  745 tests, 0 failures
      gdb gdb_6_1-branch                745 tests, 0 failures

    For gcc tests, the test results are with binutils 2.14.
    The binutils version should not make a difference.

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2004-05-09/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2004-05-03/index.html

  . Non-Pass Results

    gdb 6.1
      suite 6.1                           1032 non-PASS results
      suite HEAD                          1071 non-PASS results
    gdb gdb_6_1-banch
      suite gdb_6_1-branch                1033 non-PASS results
      suite HEAD                          1064 non-PASS results
    gdb HEAD
      suite HEAD                          1107 non-PASS results
    gdb drow_intercu-20040221-branch
      suite drow_intercu-20040221-branch  1041 non-PASS results
      suite HEAD                          1073 non-PASS results

    I run each version of gdb with two test suites: the test suite that
    comes with that version of gdb and the test suite that comes with
    gdb HEAD.

  . gdb 6.1

    . suite 6.1

      . gdb.base/bigcore.exp: extract next heap
        gdb.base/bigcore.exp: extract prev heap
          PASS -> blank
        gdb.base/bigcore.exp: extract next heap (stop at 50)
        gdb.base/bigcore.exp: extract prev heap (stop at 50)
          blank -> PASS

          Not analyzed.  Probably harmless.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    6  71  69  68  70  72
            FAIL   66   1   3   4   2   0

  . gdb 6.1

    . suite HEAD

      . gdb.base/auxv.exp: *
          blank -> PASS
          WARNING -> blank
          FAIL -> PASS
          UNSUPPORTED -> PASS
          UNSUPPORTED -> FAIL

          This is a bug in the test script.

            http://sources.redhat.com/gdb/bugs/1647
            gdb.base/auxv.exp, incomplete input consumption

      . gdb.base/lineinc.exp: tolerate macro info with multiple #inclusions  per line
          blank -> PASS

          Jim B wrote a new test script.

      . gdb.base/pending.exp: *
          blank -> PASS
        gdb.base/pending.exp: continue to resolved breakpoint 1
        gdb.base/pending.exp: continue to resolved breakpoint 2
          PASS -> FAIL
        gdb.base/pending.exp: continue to resolved breakpoint 3
          blank -> FAIL

          Jim I added some new tests.  The new tests reveal some bugs with
          breakpoint numbers in gdb 6.1, gdb gdb_6_1-branch, and gdb
          drow_intercu-20040221-branch; but all results are PASS with gdb
          HEAD.  These are good tests.

      . gdb.threads/print-threads.exp: *
          blank -> ERROR
          blank -> FAIL
          blank -> UNRESOLVED
          PASS -> blank
          PASS -> FAIL
          KFAIL -> blank

          A stray "Quit" popped up during one configuration.  This might
          be an instance of PR gdb/1636, but it might also be a
          different bug.
          
            http://sources.redhat.com/gdb/bugs/1636
            manythreads.exp issues async ^C that spills onto next script

          In other incidents of gdb/1636, manythreads.exp reports some
          FAIL results and then leaves an asynchronous ^C in the
          background to derail the next script, print-threads.exp.  In
          this incident, all results from manythreads.exp were PASS, but
          an extra ^C popped up in print-threads.exp anyways.

          We have to fix gdb/1636 and then see if this still occurs.
          I have a patch waiting for review for this bug.

      . gdb.base/sep.exp: breakpoint inside included file
        gdb.base/sep.exp: list using location inside included file
          KFAIL -> FAIL
        gdb.base/sep.exp: dummy command to set the current source file
          PASS -> blank

          Joel B removed the KFAIL machinery from the test script.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    0  14  14  14  14  14
            FAIL   14   0   0   0   0   0

  . gdb gdb_6_1-branch

    . suite gdb_6_1-branch

      . gdb.base/selftest.exp: printed version as string
          PASS -> blank
        gdb.base/selftest.exp: printed version
          blank -> FAIL

          This is a bug in the machinery which updates version.in,
          the version string of gdb.

            http://sources.redhat.com/gdb/bugs/1648
            version.in corrupted on gdb_6_1-branch
          
      . gdb.cp/annota2.exp: annotate-quit
          KFAIL -> PASS
        gdb.cp/annota3.exp: annotate-quit
          FAIL -> PASS

          Fluctuation in test result probably due to a signal handling
          race in the command loop.

            http://sources.redhat.com/gdb/bugs/544
            gdb.c++/annota2.exp: annotate-quit test sometimes fails

      . gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
        gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
          PASS -> blank

          Fluctuation with unknown cause.  Probably harmless.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS   15  65  69  65  66  72
            FAIL   57   7   3   7   6   0

  . gdb gdb_6_1-branch

    . suite HEAD

      . gdb.base/lineinc.exp: tolerate macro info with multiple #inclusions  per line
          blank -> PASS

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/pending.exp: *
          blank -> PASS
        gdb.base/pending.exp: continue to resolved breakpoint 1
        gdb.base/pending.exp: continue to resolved breakpoint 2
          PASS -> FAIL
        gdb.base/pending.exp: continue to resolved breakpoint 3
          blank -> FAIL

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/selftest.exp: printed version as string
          PASS -> blank
        gdb.base/selftest.exp: printed version
          blank -> FAIL

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/sep.exp: breakpoint inside included file
        gdb.base/sep.exp: list using location inside included file
          KFAIL -> FAIL
        gdb.base/sep.exp: dummy command to set the current source file
          PASS -> blank

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.cp/annota3.exp: annotate-quit
          PASS -> FAIL

          Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    1  14  14  14  13  14
            FAIL   13   0   0   0   1   0

  . gdb HEAD

    . suite HEAD

      . gdb.base/bigcore.exp: extract next heap
        gdb.base/bigcore.exp: extract prev heap
          PASS -> blank
        gdb.base/bigcore.exp: extract next heap (stop at 50)
        gdb.base/bigcore.exp: extract prev heap (stop at 50)
          blank -> PASS

          Same analysis as gdb 6.1 suite 6.1.

      . gdb.base/lineinc.exp: tolerate macro info with multiple #inclusions  per line
          blank -> PASS

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/pending.exp: *
          blank -> PASS

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/sep.exp: breakpoint inside included file
        gdb.base/sep.exp: list using location inside included file
          KFAIL -> FAIL
          KFAIL -> PASS
        gdb.base/sep.exp: dummy command to set the current source file
          PASS -> blank

          Joel B removed the KFAIL machinery from the test script.
          
          These versions of gcc now have FAIL results:
            2.95.3 3.4.0 gcc-3_4-branch HEAD tree-ssa-20020619-branch

          These versions of gcc now have PASS results:
            3.2.7-rh 3.3.3 gcc-3_3-branch

      . gdb.base/structs.exp: return and finish use same convention; return * structs-*
          PASS -> KFAIL

          This test checks that two mechanisms in gdb have the same
          behavior: both work or neither works.  In the last spin,
          "return" did not work and "finish" did not work.
          In this spin, "return" still does not work, but "finish" works.

            http://sources.redhat.com/gdb/bugs/1444
            Return-value struct convention doesn't work with finish or return

          This KFAIL happened in every configuration tested.

          I'm not sure whether this is a real regression in gdb.
          I will treat as such for now and ask Andrew C about it.

      . gdb.cp/annota3.exp: annotate-quit
          FAIL -> PASS

          Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.

      . gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          blank -> PASS
          PASS -> blank
        gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
        gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
          FAIL -> blank
          blank -> FAIL

          This is a bug in gdb.  It happens intermittently.

            http://sources.redhat.com/gdb/bugs/1650
            manythreads.exp

      . gdb.threads/print-threads.exp: *
          blank -> ERROR
          blank -> PASS
          blank -> FAIL
          blank -> KFAIL
          blank -> UNRESOLVED
          ERROR -> blank
          PASS -> blank
          PASS -> FAIL
          FAIL -> blank
          FAIL -> PASS
          FAIL -> UNRESOLVED
          KFAIL -> blank
          UNRESOLVED -> blank
          UNRESOLVED -> PASS

          This is a cascade problem from the previous script,
          manythreads.exp.

            http://sources.redhat.com/gdb/bugs/1636
            manythreads.exp issues async ^C that spills onto next script

          This script also gives erratic results even when manythreads.exp
          does not change its behavior.  I didn't analyze all the cases.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS   18  64  69  72  63  72
            FAIL   54   8   3   0   9   0

  . gdb drow_intercu-20040221-branch

    . suite drow_intercu-20040221-branch

      . gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
          PASS -> blank

          Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    3  13  13  12  13  14
            FAIL   11   1   1   2   1   0

  . gdb drow_intercu-20040221-branch

    . suite HEAD

      . gdb.base/lineinc.exp: tolerate macro info with multiple #inclusions  per line
          blank -> PASS

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/pending.exp: *
          blank -> PASS
        gdb.base/pending.exp: continue to resolved breakpoint 1
        gdb.base/pending.exp: continue to resolved breakpoint 2
          PASS -> FAIL
        gdb.base/pending.exp: continue to resolved breakpoint 3
          blank -> FAIL

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.base/sep.exp: breakpoint inside included file
        gdb.base/sep.exp: list using location inside included file
          KFAIL -> FAIL
        gdb.base/sep.exp: dummy command to set the current source file
          PASS -> blank

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.cp/annota2.exp: annotate-quit
          KFAIL -> PASS

          Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.

      . gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          blank -> PASS
          PASS -> blank
        gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
        gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
          blank -> FAIL
          FAIL -> blank

          Same analysis as gdb HEAD suite HEAD.

      . gdb.threads/print-threads.exp: *
          blank -> ERROR
          blank -> PASS
          blank -> FAIL
          blank -> KFAIL
          blank -> UNRESOLVED
          ERROR -> blank
          PASS -> blank
          PASS -> FAIL
          FAIL -> blank
          FAIL -> PASS
          KFAIL -> blank
          UNRESOLVED -> blank
          UNRESOLVED -> PASS

          Same analysis as gdb 6.1 suite HEAD.

      . gdb.threads/schedlock.exp: *
          PASS
        gdb.threads/schedlock.exp: thread 0 ran (didn't run)
        gdb.threads/schedlock.exp: thread 1 ran (didn't run)
        gdb.threads/schedlock.exp: thread 2 ran (didn't run)
        gdb.threads/schedlock.exp: thread 3 ran (didn't run)
        gdb.threads/schedlock.exp: thread 4 ran (didn't run)
        gdb.threads/schedlock.exp: thread 5 ran (didn't run)
          PASS
          FAIL

          All tests PASSed in all configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    3  12  14  14  12  14
            FAIL   11   2   0   0   2   0

. Package Versions

  . This Spin

    binutils  HEAD                          2004-05-07 11:18:29 UTC
    binutils  binutils-2_15-branch          2004-05-07 11:20:25 UTC
    gcc       tree-ssa-20020619-branch      2004-05-07 11:45:33 UTC
    gcc       HEAD                          2004-05-07 11:56:13 UTC
    gcc       gcc-3_4-branch                2004-05-07 12:06:39 UTC
    gcc       gcc-3_3-branch                2004-05-07 12:20:08 UTC
    gdb       HEAD                          2004-05-10 00:22:49 UTC
    gdb       drow_intercu-20040221-branch  2004-05-10 00:27:23 UTC
    gdb       gdb_6_1-branch                2004-05-10 01:52:27 UTC

  . Last Spin

    binutils  HEAD                          2004-05-01 10:31:18 UTC
    binutils  binutils-2_15-branch          2004-05-01 10:33:30 UTC
    gcc       tree-ssa-20020619-branch      2004-05-01 10:48:41 UTC
    gcc       HEAD                          2004-05-01 10:56:51 UTC
    gcc       gcc-3_4-branch                2004-05-01 11:03:34 UTC
    gcc       gcc-3_3-branch                2004-05-01 11:11:25 UTC
    gdb       HEAD                          2004-05-03 13:01:38 UTC
    gdb       drow_intercu-20040221-branch  2004-05-03 13:08:00 UTC
    gdb       gdb_6_1-branch                2004-05-03 13:10:15 UTC

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  dejagnu    => dejagnu 1.4.4
  expect     => expect 5.41
  tcl        => tcl 8.4.6
  gdb        => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
  suite      => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
  as         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.91, binutils 2.14.92, binutils binutils-2_15-branch, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.91, binutils 2.14.92, binutils binutils-2_15-branch, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count      => 272

  'target' and 'host' are gnu configuration triples.

  'osversion' is the host operating system name, which is additional
  information beyond 'host'.

  'tcl', 'expect', and 'dejagnu' are host packages to run tests.

  'suite' is the version name of the gdb test suite.

  'gdb' is a version name.

  'cc', 'as', 'ld', and 'libc' are package names.

  versions starting with a digit are official releases or snapshots.
  versions starting with a digit and ending with '-rh' are
    vendor-supplied official releases on my red hat linux host.
  versions named 'HEAD' are the cvs HEAD, also known as 'mainline' or 'trunk'.
  versions with any other name are cvs branches.

  'gformat' is the debugging information format.
  'glevel' is the debugging level.

  'count' is the total number of configurations tested.

  as/ld are always matched.

  The vendor gcc is available only with vendor as/ld.

  The vendor as/ld are tested only with vendor gcc.

  I test gdb 6.1 suite 6.1, gdb gdb_6_1-branch suite gdb_6-1-branch, and
  gdb HEAD suite HEAD with the full spectrum of as and ld.  I test other
  gdb/suite configurations only with as binutils 2.14 and ld binutils
  2.14.

. Host Software

  . host=i686-pc-linux-gnu, osversion=red-hat-8.0

    make 3.79.1
    binutils 2.14
    gcc 3.3.2
    flex 2.5.4
    bison 1.875
    texinfo 4.7
    tcl 8.4.6
    expect 5.41
    dejagnu 1.4.4

  The sources.redhat.com cvs repository has its own versions of tcl,
  expect, and dejagnu.  I don't have the resources to test with both
  tcl/expect/dejagnu stacks, so I choose the stock stack for my test
  bed.
  
  The sources.redhat.com version of tcl is nearly identical to tcl
  8.4.1.  The sources.redhat.com version of expect dates from
  1998-06-15.  The sources.redhat.com version of dejagnu is nearly
  identical to dejagnu 1.4.3.

  I have packaged and published my scripts to manage the baseline
  software.  They are called Migchain (Michael's Gnu Toolchain) and
  Migbat (Michael's Gnu Build and Test), and they are licensed under the
  GPL.

    ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.8.tar.gz
    ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.8.tar.gz

. Test Bed Changes Since Last Report

  I added binutils 2.14.92.

  This is the last spin for binutils 2.14.91.


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