Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][PR 18702] Fix wrong output of x87 registers due to truncation to double on amd64
Date: Fri, 04 Dec 2015 15:17:00 -0000	[thread overview]
Message-ID: <CAHEcG96YEnYnBevsNcz71553u9LsWU5tZFxpRzNcLz0eDNXrow@mail.gmail.com> (raw)
In-Reply-To: <5661AD07.5090002@redhat.com>

On Fri, Dec 4, 2015 at 6:11 PM, Pedro Alves <palves@redhat.com> wrote:
> On 12/04/2015 03:06 PM, Ruslan Kabatsayev wrote:
>> On Thu, Dec 3, 2015 at 3:28 PM, Pedro Alves <palves@redhat.com> wrote:
>>> A test to make sure we don't regress this would be nice.
>>> Maybe add something to gdb.arch/i386-float.exp ?
>>
>> I think I'll do this. Should this go as a separate patch?
>
> Ideally it'd go in the same patch.
Oh, OK. What about email subject? Can I just send it as a follow-up to
this conversation, or does it have to be an independent email with
subject="[PATCH]..."? Or is there no difference?
(Sorry for silly questions, I'm just trying to fulfill all the
requirements at the first try :) )

>
> Thanks,
> Pedro Alves
>


  reply	other threads:[~2015-12-04 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 22:07 Ruslan Kabatsayev
2015-12-02 11:32 ` Yao Qi
2015-12-02 14:26   ` Ruslan Kabatsayev
2015-12-03 11:27     ` Yao Qi
2015-12-04 14:41       ` Ruslan Kabatsayev
2015-12-03 12:28 ` Pedro Alves
2015-12-04 15:06   ` Ruslan Kabatsayev
2015-12-04 15:11     ` Pedro Alves
2015-12-04 15:17       ` Ruslan Kabatsayev [this message]
2015-12-04 15:35         ` Pedro Alves
2015-12-04 16:09           ` Ruslan Kabatsayev
2015-12-05 22:41             ` Andrew Burgess
2015-12-06  6:30               ` Ruslan Kabatsayev
2015-12-09 12:23                 ` Pedro Alves

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=CAHEcG96YEnYnBevsNcz71553u9LsWU5tZFxpRzNcLz0eDNXrow@mail.gmail.com \
    --to=b7.10110111@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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