From: Josh Triplett <josht@linux.vnet.ibm.com>
To: Michael Stefaniuc <mstefani@redhat.com>
Cc: josh@freedesktop.org, linux-sparse@vger.kernel.org
Subject: Re: Warnings while compiling sparse
Date: Mon, 30 Jul 2007 14:24:25 -0700 [thread overview]
Message-ID: <1185830665.3334.27.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <20070730203027.GA21099@redhat.com>
On Mon, 2007-07-30 at 22:30 +0200, Michael Stefaniuc wrote:
> Hell Josh,
Hello to you too. :)
> commit 06bcf19cb8eb3cc3154ba6131477d742a9f0b4b6
> Author: Josh Triplett <josh@freedesktop.org>
> Date: Sun Jul 29 20:20:38 2007 -0700
>
> Makefile: Use -O2 -finline-functions, not just -O
>
> introduces warnings while compiling sparse on my machine (FC6, x86,
> gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)):
Yes, it does here too. All of this comes from the ptrlist code, which
does indeed break the C99 strict-aliasing rules in its pointer casts.
Either we need -fno-strict-aliasing or we need to type-pun through a
union; we most likely want the latter, though it'll uglify the ptrlist
code.
- Josh Triplett
next prev parent reply other threads:[~2007-07-30 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:30 Warnings while compiling sparse Michael Stefaniuc
2007-07-30 21:24 ` Josh Triplett [this message]
2007-07-30 22:06 ` Michael Stefaniuc
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=1185830665.3334.27.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mstefani@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