From: Maciej Soltysiak <solt@dns.toxicfilms.tv>
To: Rudmer van Dijk <rudmer@legolas.dynup.net>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm4
Date: Thu, 5 Jun 2003 11:21:29 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.51.0306051120250.17494@dns.toxicfilms.tv> (raw)
In-Reply-To: <200306042333.26850.rudmer@legolas.dynup.net>
> I got the following errors with every file that includes
> include/linux/bitops.h
>
> include/linux/bitops.h: In function `generic_hweight64':
> include/linux/bitops.h:118: warning: integer constant is too large for "long"
> type
> include/linux/bitops.h:118: warning: integer constant is too large for "long"
> type
> include/linux/bitops.h:119: warning: integer constant is too large for "long"
<snip>
Same here with debian unstable with gcc-3.3, it started to act like that
since -mm4, mm3 was ok.
> This is on UP, athlon, gcc 3.3
Also UP on P4.
Regards,
Maciej
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2003-06-05 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 6:18 2.5.70-mm4 Andrew Morton
2003-06-04 8:12 ` 2.5.70-mm4 RAID1 seems to work! Helge Hafting
2003-06-04 13:55 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:33 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:52 ` 2.5.70-mm4 Paul Larson
2003-06-04 18:00 ` 2.5.70-mm4 Felipe Alfaro Solana
2003-06-04 17:14 ` 2.5.70-mm4 Alexander Hoogerhuis
2003-06-04 21:12 ` 2.5.70-mm4 Helge Hafting
2003-06-05 1:53 ` 2.5.70-mm4 Neil Brown
2003-06-05 15:24 ` 2.5.70-mm4 this helped but still no raid0 Helge Hafting
2003-06-04 21:33 ` 2.5.70-mm4 Rudmer van Dijk
2003-06-05 9:21 ` Maciej Soltysiak [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=Pine.LNX.4.51.0306051120250.17494@dns.toxicfilms.tv \
--to=solt@dns.toxicfilms.tv \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rudmer@legolas.dynup.net \
/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