From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: mec@shout.net
Cc: ac131313@redhat.com, drow@mvista.com, gdb@sources.redhat.com
Subject: Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
Date: Sat, 18 Jan 2003 11:33:00 -0000 [thread overview]
Message-ID: <9743-Sat18Jan2003133115+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200301172028.h0HKS1006718@duracef.shout.net> (message from Michael Elizabeth Chastain on Fri, 17 Jan 2003 14:28:01 -0600)
> Date: Fri, 17 Jan 2003 14:28:01 -0600
> From: Michael Elizabeth Chastain <mec@shout.net>
>
> Andrew C writes:
> > If the bug is fixed in GCC we might as well indicate this by closing our
> > side of the bug report. No reason to hang onto a bug report that has
> > been resolved.
>
> Does this include the XFAIL's for gcc v2 stabs+ in gdb.base/constvars.exp?
>
> I really think that it's a year too early to close a gdb bug report
> with gcc 2.95.3 by saying "it works if you use gcc 3.X".
I agree.
I also think that if we introduce new bugs in some feature which did
support older compilers, that bug should be fixed, even if it's not
exposed by newer GCC versions.
next prev parent reply other threads:[~2003-01-18 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 20:28 Michael Elizabeth Chastain
2003-01-18 11:33 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 20:52 Michael Elizabeth Chastain
2003-01-17 20:03 Michael Elizabeth Chastain
2003-01-17 19:57 Michael Elizabeth Chastain
2003-01-17 19:45 Michael Elizabeth Chastain
2003-01-17 19:46 ` Daniel Jacobowitz
2003-01-17 20:12 ` Andrew Cagney
2003-01-17 20:18 ` Daniel Jacobowitz
2003-01-17 20:53 ` Andrew Cagney
2003-01-17 22:06 ` Daniel Jacobowitz
2003-01-17 23:28 ` Andrew Cagney
2003-01-18 3:40 ` Daniel Jacobowitz
2003-01-17 20:16 ` Andrew Cagney
2003-01-16 19:35 Andrew Cagney
2003-01-17 19:26 ` Andrew Cagney
2003-01-17 19:29 ` Daniel Jacobowitz
2003-01-17 19:47 ` Andrew Cagney
2003-01-17 19:40 ` David Carlton
2003-01-17 19:56 ` Andrew Cagney
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=9743-Sat18Jan2003133115+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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