From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: gdb 5.3 versus gdb HEAD%200302015
Date: Mon, 17 Feb 2003 16:35:00 -0000 [thread overview]
Message-ID: <20030217163501.GA17952@nevyn.them.org> (raw)
In-Reply-To: <200302171632.h1HGWUj12060@duracef.shout.net>
On Mon, Feb 17, 2003 at 10:32:30AM -0600, Michael Elizabeth Chastain wrote:
> drow> Ooh ooh. I got this one. The test is new in HEAD (wasn't in 5.3);
> drow> it's a GCC bug; it will be fixed in 3.3, 3.4, and 3.2.3 if any. I
> drow> checked the patch in the day after 3.2.2.
>
> Beautiful, I'll just slip a URL to this message into my tracking
> document. That takes care of the 5.4/6.0 angle.
>
> My results are:
>
> PASS for all stabs+
> PASS for dwarf-2, gcc gcc-3_3-branch and gcc HEAD
> FAIL for dwarf-2, gcc 2.95.3 and gcc 3.2-7-rh and gcc 3.2.2
>
> Which matches your report.
>
> I dropped coverage of gcc gcc-3_2-branch, but I might bring it back,
> because I see that people are still checking into that branch.
>
> The real question: is there a gcc PR for this. If there is a gcc PR,
> then I can add an XFAIL arm to the test with the gcc PR number.
Nope, there was no PR, just a patch when I noticed it. Besides, didn't
we want to only use PRs in the GDB database? This would be an
external/closed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-17 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:32 Michael Elizabeth Chastain
2003-02-17 16:35 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 17:08 Michael Elizabeth Chastain
2003-02-17 17:13 ` David Carlton
2003-02-17 17:02 Michael Elizabeth Chastain
2003-02-17 16:44 Michael Elizabeth Chastain
2003-02-17 16:50 ` Daniel Jacobowitz
2003-02-17 15:32 Michael Elizabeth Chastain
2003-02-17 15:39 ` Daniel Jacobowitz
2003-02-17 17:03 ` David Carlton
2003-02-18 14:59 ` Michal Ludvig
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=20030217163501.GA17952@nevyn.them.org \
--to=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