[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.5.70-mm4

To: Rudmer van Dijk <rudmer@legolas.dynup.net>
Subject: Re: 2.5.70-mm4
From: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Date: Thu, 5 Jun 2003 11:21:29 +0200 (CEST)
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org,linux-mm@kvack.org
Fake-Sender: owner-linux-mm@kvack.org
In-Reply-To: <200306042333.26850.rudmer@legolas.dynup.net>
Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
References: <20030603231827.0e635332.akpm@digeo.com><200306042333.26850.rudmer@legolas.dynup.net>
Sender: Rik van Riel <riel@nl.linux.org>

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

References:
- 2.5.70-mm4
  - From: Andrew Morton <akpm@digeo.com>
- Re: 2.5.70-mm4
  - From: Rudmer van Dijk <rudmer@legolas.dynup.net>

Prev by Date: 2.5.70-mm5
Next by Date: Re: 2.5.70-mm5 new oops that wasn't in 2.5.70-mm4
Prev by thread: Re: 2.5.70-mm4
Next by thread: [PATCH] Remove page_table_lock from vma manipulations
Index(es):
- Date
- Thread