Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ruslan Kabatsayev <b7.10110111@gmail.com>
To: Yao Qi <qiyaoltc@gmail.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: Wed, 02 Dec 2015 14:26:00 -0000	[thread overview]
Message-ID: <CAHEcG95HeiLdhXFP0Zy8nz=dE9divExtau+OUg=NXo+Sb_zHfg@mail.gmail.com> (raw)
In-Reply-To: <86mvttt7be.fsf@gmail.com>

Hi Yao,

Thanks for your reply.

On Wed, Dec 2, 2015 at 2:32 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> I think your patch is correct, but I am not confident approving it
> because I know few about floating point stuff.  Do you run GDB
> regression tests?

I did a `make check` for unpatched gdb-7.10 and patched with my
changes. Here's the unpatched result:

# of expected passes            32377
# of unexpected failures        85
# of unexpected successes       2
# of expected failures          72
# of unknown successes          2
# of known failures             62
# of untested testcases         36
# of unsupported tests          201

And here's after my patch:

# of expected passes            32378
# of unexpected failures        85
# of unexpected successes       2
# of expected failures          71
# of unknown successes          2
# of known failures             62
# of untested testcases         36
# of unsupported tests          201

I.e. one "expected failure" less and one "expected pass" more. I'm not
sure how to interpret this result.

>> gdb/ChangeLog:
>>
>>       * configure.host: Fix detection of x86_64 host when setting floatformats
>
> This line is too long, the max is 74.  Sentence should be ended with ".".

Should I resend the whole original mail with this fixed?

Regards,
Ruslan


  reply	other threads:[~2015-12-02 14:26 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 [this message]
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
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='CAHEcG95HeiLdhXFP0Zy8nz=dE9divExtau+OUg=NXo+Sb_zHfg@mail.gmail.com' \
    --to=b7.10110111@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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