From: Yao Qi <qiyaoltc@gmail.com>
To: Ruslan Kabatsayev <b7.10110111@gmail.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][PR 18702] Fix wrong output of x87 registers due to truncation to double on amd64
Date: Thu, 03 Dec 2015 11:27:00 -0000 [thread overview]
Message-ID: <86610fu60p.fsf@gmail.com> (raw)
In-Reply-To: <CAHEcG95HeiLdhXFP0Zy8nz=dE9divExtau+OUg=NXo+Sb_zHfg@mail.gmail.com> (Ruslan Kabatsayev's message of "Wed, 2 Dec 2015 17:26:19 +0300")
Ruslan Kabatsayev <b7.10110111@gmail.com> writes:
> I did a `make check` for unpatched gdb-7.10 and patched with my
> changes. Here's the unpatched result:
Thanks for running the test. Could you test your patch against GDB git
mainline please? The patch will be applied to mainline, so we need to
test it against mainline.
>
> # 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.
>
This may happen from time to time, especially in some gdb.threads tests.
>>> 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?
Please post the changelog entry only for the reference.
If there is no regression in the GDB mainline tests, and no objections
from other people in 3 days, your patch can go in.
Do you have write access to git repository and FSF copyright assignment?
If you don't have them, I can commit it for you as a tiny patch.
However, if you want to contribute more patches, you need an FSF
copyright assignment, and git write access, so that you can push by yourself.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-12-03 11:27 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 [this message]
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=86610fu60p.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=b7.10110111@gmail.com \
--cc=gdb-patches@sourceware.org \
/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