From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: quick status on gdb-7.2.1 & gdb-7.3? (Mar 07)
Date: Mon, 07 Mar 2011 12:43:00 -0000 [thread overview]
Message-ID: <20110307122732.GC2478@adacore.com> (raw)
Hello everyone,
It's been a while since we last really talked about the release,
can we have a quick status on the various items we're waiting for?
Right now, we're about 3 weeks late.
- The big blockers for the release are (regressions) [Keith, Jan]:
c++/11734
c++/12273
It sounded like Keith and Jan are making progress, and getting
closer to a solution that doesn't introduces other regressions.
How far do we think we are?
For GDB 7.3, we have, in addition to the above:
- ifunc branch (might be close to being merge-ready) [Jan]
- exposing SystemTap static probe points [Sergio, Tom]
- tracepoint printf support [Hui] (awaiting review)
- <unavailable> values support (part 3) [Pedro]
http://sourceware.org/ml/gdb-patches/2011-02/msg00581.html
http://sourceware.org/ml/gdb-patches/2011-02/msg00611.html
It's been waiting for comments a while, now, so should be
ready to commit soon?
My understanding is that we don't really need to wait for the
ifunc and SystemTap stuff if it's going to delay the release.
Only a nice to have.
I don't think that Hui's tracepoint printf patch is a critical
patch either, but it's been waiting for review for a while, now,
and it'd be nice to at least review it before we branch. Anyone,
competent in this area, please?
So, all in all, I think we're just blocked by the C++ regressions.
As soon as they are resolved, we can start thinking about branching.
--
Joel
next reply other threads:[~2011-03-07 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 12:43 Joel Brobecker [this message]
2011-03-07 14:47 ` Joel Brobecker
2011-03-07 22:26 ` Tom Tromey
2011-03-08 8:26 ` Joel Brobecker
2011-03-08 10:02 ` Jan Kratochvil
2011-03-08 18:38 ` Jan Kratochvil
2011-03-09 5:29 ` 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=20110307122732.GC2478@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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