From: David Woodhouse <dwmw2@infradead.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Add GCC's byteswap intrinsics
Date: Thu, 13 Dec 2012 16:29:31 +0000 [thread overview]
Message-ID: <1355416171.19560.47.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20121213161119.GA8149@leaf>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Thu, 2012-12-13 at 08:11 -0800, Josh Triplett wrote:
>
> GCC defines these to use int16_t, int32_t, and int64_t, respectively.
> The first two of those should match up to "short" and "int" without any
> issue, but on 64-bit platforms, stdint.h defines int64_t as "long", not
> "long long". That could lead to some type incompatibilities.
Are we allowed to use int64_t? Or must we pretend that it's still the
20th century and stdint.h might not be present?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
prev parent reply other threads:[~2012-12-13 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 13:45 [PATCH] Add GCC's byteswap intrinsics David Woodhouse
2012-12-13 16:11 ` Josh Triplett
2012-12-13 16:29 ` David Woodhouse [this message]
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=1355416171.19560.47.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).