From: Logan Gunthorpe <logang@deltatee.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v2] add __builtin functions for isinf_sign, isfinite and isnan
Date: Thu, 16 Nov 2017 18:04:56 -0700 [thread overview]
Message-ID: <f37fa631-edac-8de1-1cb4-4bd1edd807b2@deltatee.com> (raw)
In-Reply-To: <CANeU7Q=hr0OKtHk1gVsN2q1qzUxJ6URFsOY+YQtu_ThrB8UenA@mail.gmail.com>
On 11/16/2017 5:02 PM, Christopher Li wrote:
> In the history we are having header file issue with cygwin and other compile
> environment due to sparse don't understand other system macros. It is
> better to have sparse able to run the validations test without have to fix
> every single system macro define. It is kind of expect to be broken on new
> and untested platform. There for, best to have no system header in the
> validation test.
Fair enough,
Thanks.
Logan
next prev parent reply other threads:[~2017-11-17 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 23:08 [PATCH v2] add __builtin functions for isinf_sign, isfinite and isnan Logan Gunthorpe
2017-11-17 0:02 ` Christopher Li
2017-11-17 1:04 ` Logan Gunthorpe [this message]
2017-11-17 8:13 ` Luc Van Oostenryck
2017-11-17 23:28 ` Luc Van Oostenryck
2017-11-17 23:39 ` Logan Gunthorpe
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=f37fa631-edac-8de1-1cb4-4bd1edd807b2@deltatee.com \
--to=logang@deltatee.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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