From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Skip float complex types if gdb_skip_float_test
Date: Tue, 04 Oct 2016 18:49:00 -0000 [thread overview]
Message-ID: <c0d6534c-a740-f066-2bee-e702df9bcc5a@redhat.com> (raw)
In-Reply-To: <1475591646-9783-1-git-send-email-yao.qi@linaro.org>
On 10/04/2016 03:34 PM, Yao Qi wrote:
> If the target doesn't support float, we don't run float complex types
> tests.
Shouldn't this be checked within support_complex_tests itself?
AFAIK, _Complex is always about floating point:
http://en.cppreference.com/w/c/language/arithmetic_types#Complex_floating_types
http://en.cppreference.com/w/cpp/numeric/complex
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-10-04 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 14:34 Yao Qi
2016-10-04 18:49 ` Pedro Alves [this message]
2016-10-05 13:47 ` Yao Qi
2016-10-05 14:07 ` Pedro Alves
2016-10-05 16:06 ` Yao Qi
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=c0d6534c-a740-f066-2bee-e702df9bcc5a@redhat.com \
--to=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).