From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, mishra.nitish.88@gmail.com,
Pedro Alves <palves@redhat.com>,
Antoine Tremblay <antoine.tremblay@ericsson.com>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: GDB 8.0 release/branching update (10 more days to branching)
Date: Thu, 09 Mar 2017 18:52:00 -0000 [thread overview]
Message-ID: <m3variffl1.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <20170304175903.qwbqoqm35raz4dov@adacore.com> (Joel Brobecker's message of "Sat, 4 Mar 2017 18:59:03 +0100")
On Sat, Mar 04 2017, Joel Brobecker wrote:
> Hello everyone,
>
> We are now about 10 days away from our tentative date for branching.
> First of all, a big thank you for all of you who fixed some of those
> PRs that were marked for 8.0!
Probably a bit late, but I'd also like to get these fixes upstream
before the branch:
* gdb/21220 "restore" for large data structures extremely slow on
GNU/Linux
A regression from last year that renders "restore" for large data
structures unusable on GNU/Linux. Proposed fix is available.
* gdb/21226 DW_OP_stack_value pieces yield wrong data on big-endian
targets
Causes wrong values to be displayed for certain variables on big-endian
targets. Not a recent regression, but potentially causes severe
headaches for people running into it. Proposed fix is available.
--
Andreas
prev parent reply other threads:[~2017-03-09 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 17:59 Joel Brobecker
2017-03-04 22:16 ` Yao Qi
2017-03-07 0:26 ` Joel Brobecker
2017-03-07 15:06 ` Pedro Alves
2017-03-09 18:52 ` Andreas Arnez [this message]
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=m3variffl1.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=palves@redhat.com \
--cc=uweigand@de.ibm.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