Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/dwarf2] Small problem scanning line table for included files
Date: Sun, 25 Jul 2004 22:48:00 -0000	[thread overview]
Message-ID: <410438B1.nailHRK18RQBL@mindspring.com> (raw)
In-Reply-To: <20040725151137.GT20596@gnat.com>

Now that I look, I see this happening in my test bed, too.
gdb HEAD suite HEAD -gdwarf-2 has PASS with gcc 3.3.4 and
FAIL with gcc 3.4.1.

I had better take another look at my gcc 3.3.4 versus gcc 3.4.1
tables and see if I overlooked anything else in there!

  http://www.shout.net/~mec/sunday/current/Compare-by-gcc-334-341.html

The regressions I know about are:

  gcc 3.4.1 versus gcc 3.3.4
    gcc/12267 gcc/13708 gcc/13956
    gdb/1537 gdb/1540

Michael C


  reply	other threads:[~2004-07-25 22:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25 15:11 Joel Brobecker
2004-07-25 22:48 ` Michael Chastain [this message]
2004-07-28 18:56 ` Jim Blandy
2004-07-30 19:01   ` Joel Brobecker
2004-07-30 21:18     ` Joel Brobecker
2004-08-01  7:01       ` Jim Blandy
2004-08-02  1:26         ` Joel Brobecker

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=410438B1.nailHRK18RQBL@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@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