From: "Marko Kreen" <markokr@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: Re: confusing shift warning
Date: Fri, 25 Apr 2008 11:03:09 +0300 [thread overview]
Message-ID: <e51f66da0804250103y4c5abbaby2c8a43db7ba5d04f@mail.gmail.com> (raw)
In-Reply-To: <e51f66da0804250053x2ec991dbu9a5a54fdcbea2a2a@mail.gmail.com>
On 4/25/08, Marko Kreen <markokr@gmail.com> wrote:
> Platform: x64_64 linux, uint64_t -> unsigned long
> Sparse: today's git (6dcc36a)
Oh, and another warning:
#include <sys/socket.h> gives:
/usr/include/bits/socket.h:159:5: warning: constant
9223372036854775807L is so big it is long long
I used to ignore it as it was not in my code, but its probably same thing.
Ubuntu 8.04
gcc 4:4.2.3-1ubuntu3
glibc 2.7-10ubuntu3
linux-headers - 2.6.24-16.30
--
marko
next prev parent reply other threads:[~2008-04-25 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 7:53 confusing shift warning Marko Kreen
2008-04-25 8:03 ` Marko Kreen [this message]
[not found] ` <33544769883882222@unknownmsgid>
2008-04-25 8:34 ` Marko Kreen
2008-04-25 8:58 ` Marko Kreen
[not found] ` <-3423297637585954490@unknownmsgid>
2008-04-25 13:37 ` Marko Kreen
[not found] ` <-8184754938437793631@unknownmsgid>
2008-04-25 14:37 ` Marko Kreen
2008-04-25 16:04 ` Pavel Roskin
2008-04-25 17:26 ` Marko Kreen
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=e51f66da0804250103y4c5abbaby2c8a43db7ba5d04f@mail.gmail.com \
--to=markokr@gmail.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).