From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>, Keith Seitz <keiths@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: 2 weeks to GDB 7.10 tentative branching date!
Date: Wed, 03 Jun 2015 18:08:00 -0000 [thread overview]
Message-ID: <CADPb22QUXOj0OfLyw4yBH+5AQMZZRP6P7Gt8TS50q0bpDUEY-Q@mail.gmail.com> (raw)
In-Reply-To: <20150601213709.GC2631@adacore.com>
On Mon, Jun 1, 2015 at 2:37 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Hello,
>
> Just a quick reminder that we've set the tentative branching
> date for the GDB 7.10 release to June 15th, which is only
> a couple of weeks away.
>
> As in previous releases, we have a wiki page where we track all
> blocking issues before we can cut the branch:
>
> https://sourceware.org/gdb/wiki/GDB_7.10_Release
>
> If you know of anything that we should hold the branch for, please
> let us know. There are typically regressions, important features
> that need a little extra time to be completely integrated in master,
> etc.
>
> Thank you!
> --
> Joel
It would be great to resolve pr 16253 for 7.10.
We reverted a fix in the lead up to 7.8, hoping to revisit it
afterwards, but we never did. :-(
[details in the pr]
https://sourceware.org/bugzilla/show_bug.cgi?id=16253
Maybe a two step solution would be ok?
For 7.10:
1) re-add keiths patch, with the following modifications:
a) add a STRUCT vs VAR_DOMAIN indicator to .gdb_index
b) bump .gdb_index version to 9
c) modify keith's patch so that it only is enabled when either
.gdb_index is not in use or its version >= 9
(IOW we'd still have to keep symbol_matches_domain,
in some form, but use it conditionally)
For later:
2) when all producers we care about can produce v9 indices,
remove hack 1c
I'm aware of the u/i consequences of this approach
(whether examples like in 16253 would work would be
dependent upon whether the index is in use and its version).
Another thought I had is that symbol lookup has changed a
bit since 7.8. It may be possible to just reapply keith's
patch and avoid the massive perf regression differently.
Comments?
next prev parent reply other threads:[~2015-06-03 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 21:37 Joel Brobecker
2015-06-02 8:12 ` Jan Kratochvil
2015-06-02 8:16 ` Phil Muldoon
2015-06-03 17:06 ` Joel Brobecker
2015-06-03 17:13 ` Jan Kratochvil
2015-06-03 17:32 ` Joel Brobecker
2015-06-03 19:01 ` GDB Bugzilla Target Milestone 7.10 [Re: 2 weeks to GDB 7.10 tentative branching date!] Jan Kratochvil
2015-06-02 16:21 ` 2 weeks to GDB 7.10 tentative branching date! Yao Qi
2015-06-02 16:33 ` Jan Kratochvil
2015-06-02 20:45 ` Philippe Waroquiers
2015-06-03 17:38 ` Joel Brobecker
2015-06-03 20:06 ` Philippe Waroquiers
2015-06-03 18:08 ` Doug Evans [this message]
2015-06-04 17:25 ` Doug Evans
2015-06-15 13:58 ` GDB 7.10 new branching date: Jun 29th, 2015 (was: "Re: 2 weeks to GDB 7.10 tentative branching date!") Joel Brobecker
2015-07-02 15:53 ` GDB 7.10 new branching date: Jun 29th, 2015 Yao Qi
2015-07-02 17:18 ` Joel Brobecker
2015-07-03 10:23 ` Gary Benson
2015-07-06 11:11 ` Yao Qi
2015-07-06 16:37 ` 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=CADPb22QUXOj0OfLyw4yBH+5AQMZZRP6P7Gt8TS50q0bpDUEY-Q@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).