From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Tony Camuso <tcamuso@redhat.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Christopher Li <sparse@chrisli.org>
Subject: Re: sparse error on __int128
Date: Mon, 25 Jan 2016 18:47:04 +0100 [thread overview]
Message-ID: <20160125174703.GA43281@macpro.local> (raw)
In-Reply-To: <569659E9.1010703@redhat.com>
On Wed, Jan 13, 2016 at 09:06:33AM -0500, Tony Camuso wrote:
...
> >Now, of course, one could argue that sparse should also define __int128
> >on platforms where gcc define it, on x86_64 thus.
...
> So, I will apply the argument you so graciously supplied and posit that sparse
> should define __int128 on platforms where gcc defines it, e.g. x86_64. :)
>
> It doesn't seem like a very intrusive change.
Hehe :)
Feel like writing a patch for it?
Luc
next prev parent reply other threads:[~2016-01-25 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 11:32 sparse error on __int128 Tony Camuso
2016-01-05 0:08 ` Luc Van Oostenryck
2016-01-13 14:06 ` Tony Camuso
2016-01-25 17:47 ` Luc Van Oostenryck [this message]
2016-01-25 18:42 ` Tony Camuso
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=20160125174703.GA43281@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=tcamuso@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;
as well as URLs for NNTP newsgroup(s).