From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/3] teach sparse about endianness
Date: Tue, 20 Jun 2017 22:19:28 +0200 [thread overview]
Message-ID: <20170620201931.92864-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to let sparse correctly
check macros, structures, ... endian-specific.
This is done by:
1) the introduction of a pair of option flags:
-mbig-endian/-mlittle-endian
2) a set of predefined macros:
__{BIG,LITTLE}_ENDIAN__,
__ORDER_{BIG,LITTLE}_ENDIAN__ &
__BYTE_ORDER__
next reply other threads:[~2017-06-20 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 20:19 Luc Van Oostenryck [this message]
2017-06-20 20:19 ` [PATCH 1/3] teach sparse about -m{big,little}-endian Luc Van Oostenryck
2017-06-20 20:19 ` [PATCH 2/3] teach sparse about __{BIG,LITTLE}_ENDIAN__ Luc Van Oostenryck
2017-06-20 20:19 ` [PATCH 3/3] teach sparse about __BYTE_ORDER__ & __ORDER_{BIG,LITTLE}_ENDIAN__ Luc Van Oostenryck
2017-06-21 4:13 ` [PATCH 0/3] teach sparse about endianness Christopher Li
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=20170620201931.92864-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.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;
as well as URLs for NNTP newsgroup(s).