Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Michael Stefaniuc <mstefani@redhat.com>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Warnings while compiling sparse
Date: Tue, 31 Jul 2007 00:06:11 +0200	[thread overview]
Message-ID: <46AE60D3.1050602@redhat.com> (raw)
In-Reply-To: <1185830665.3334.27.camel@josh-work.beaverton.ibm.com>

Josh Triplett wrote:
> On Mon, 2007-07-30 at 22:30 +0200, Michael Stefaniuc wrote:
>> Hell Josh,
> 
> Hello to you too. :)
Duh ... I'm really sorry about that.
/me blames it on the cut'n'paste from thunderbird to mutt

bye
	michael

>> 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.


-- 
Michael Stefaniuc               Tel.: +49-711-96437-199
Sr. Network Engineer            Fax.: +49-711-96437-111
--------------------------------------------------------------------
Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart
Handelsregister: Amtsgericht Stuttgart HRB 153243
Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham,
                 Werner Knoblich

      reply	other threads:[~2007-07-30 22:06 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
2007-07-30 22:06   ` Michael Stefaniuc [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=46AE60D3.1050602@redhat.com \
    --to=mstefani@redhat.com \
    --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