From: Josh Triplett <josh@kernel.org>
To: linux-sparse@vger.kernel.org
Subject: Re: strict aliasing warnings in Sparse; -fno-strict-aliasing
Date: Thu, 06 Sep 2007 11:26:58 -0700 [thread overview]
Message-ID: <1189103218.23348.1.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <46DA522C.4010209@freedesktop.org>
On Sat, 2007-09-01 at 23:03 -0700, Josh Triplett wrote:
> In the absence of a better suggestion, I intend to make Sparse use
> -fno-strict-aliasing.
I've changed the Sparse Makefile to use -fno-strict-aliasing. Patches
welcome if someone wants to remove it and fix the warnings some other
way.
- Josh Triplett
prev parent reply other threads:[~2007-09-06 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 6:03 strict aliasing warnings in Sparse; -fno-strict-aliasing Josh Triplett
2007-09-06 18:26 ` Josh Triplett [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=1189103218.23348.1.camel@josh-work.beaverton.ibm.com \
--to=josh@kernel.org \
--cc=josht@linux.vnet.ibm.com \
--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).