From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [PING] [PATCH 0/3] Fix for PR 17808 and some related changes
Date: Mon, 02 Feb 2015 03:50:00 -0000 [thread overview]
Message-ID: <20150202035001.GH4525@adacore.com> (raw)
In-Reply-To: <87vbjp60kw.fsf@br87z6lw.de.ibm.com>
On Thu, Jan 29, 2015 at 04:58:07PM +0100, Andreas Arnez wrote:
> Ping:
>
> https://sourceware.org/ml/gdb-patches/2015-01/msg00424.html
>
> Pedro commented already, as shown below. Mark has not replied so far.
>
> Note that the PR is on the TODO list for 7.9. In my opinion at least
> patch 1 should go in 7.9; it's fairly harmless and should fix the PR.
> Patch 2 fixes a similar problem, but there might be a test gap, because
> I currently don't have access to appropriate test hardware (with AVX and
> AVX-512). And with patch 3 there's a slight chance of introducing bogus
> warnings when reading core files. Thus I'd suggest to push all three
> patches upstream, but only patch 1 into 7.9. OK?
Let's give it another week for additional comments (or request for
more time to review), and then push it to master.
For 7.9, let's confirm your assessment with Pedro. It sounds pretty
good to me.
--
Joel
next prev parent reply other threads:[~2015-02-02 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 16:28 Andreas Arnez
2015-02-02 3:50 ` Joel Brobecker [this message]
2015-02-03 14:19 ` Pedro Alves
2015-02-04 3:59 ` Joel Brobecker
2015-02-04 18:13 ` Andreas Arnez
2015-02-20 3:09 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2015-01-15 15:22 Andreas Arnez
2015-01-22 11:38 ` [PING] " Andreas Arnez
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=20150202035001.GH4525@adacore.com \
--to=brobecker@adacore.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@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).