Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: branch comparison tables
Date: Fri, 23 Jan 2004 03:39:00 -0000	[thread overview]
Message-ID: <20040123033854.DAD244B104@berman.michael-chastain.com> (raw)

> By the way, FYI: At this moment, the FAILs (only, not looking at the
> kfails at the moment) for GCC 3.4 and GCC HEAD are in several
> categories:

Well, that's what "compare by gcc" is for.

In this set of tables:

  http://www.shout.net/~mec/sunday/2004-01-19-branch

Here are the files that have a regression from gcc 3.3.2 to gcc
gcc-3_4-branch or a regression from gcc 3.3.2 to gcc HEAD,
with either gdb 6.0 or gdb HEAD:

  gdb.base/break.exp
  gdb.base/scope.exp
  gdb.base/sepdebug.exp
  gdb.base/store.exp
  gdb.cp/anon-union.exp
  gdb.cp/classes.exp
  gdb.cp/local.exp
  gdb.cp/namespace.exp
  gdb.java/jmisc1.exp
  gdb.java/jmisc2.exp
  gdb.mi/mi-until.exp
  gdb.mi/mi-var-block.exp
  gdb.mi/mi1-until.exp
  gdb.mi/mi1-var-block.exp
  gdb.mi/mi2-until.exp
  gdb.mi/mi2-var-block.exp
  gdb.threads/tls.exp

> I believe that no more of them are caused by GCC.

PR gcc/12267 is still causing stabs problems.
gdb.cp/anon-union.exp is blowing up, I haven't analyzed it yet.

> The multi_line_while_statement failures in your tables were, but I
> checked in a fix this morning.

That will show up in my next spin, 36-48 hours from now.

Michael C


             reply	other threads:[~2004-01-23  3:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  3:39 Michael Elizabeth Chastain [this message]
2004-01-23  5:01 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2004-01-22 23:08 Michael Elizabeth Chastain
2004-01-23  0:43 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040123033854.DAD244B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox