From: Christoph Lameter <clameter@sgi.com>
To: Martin Bligh <mbligh@mbligh.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: SLUB: Use ilog2 instead of series of constant comparisons.
Date: Wed, 6 Jun 2007 13:52:01 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706061349451.12665@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <46671C16.9080409@mbligh.org>
On Wed, 6 Jun 2007, Martin Bligh wrote:
> > I tried to build gcc-3.3.3 the other day. Would you believe that gcc-4.1.0
> > fails to compile gcc-3.3.3?
>
> IIRC, the SUSE ones were customized anyway, so not sure that'd help you.
> Might do though.
Tried building with gcc-3.3
clameter@schroedinger:~/software/slub$ powerpc-linux-gnu-gcc --version
powerpc-linux-gnu-gcc (GCC) 3.3.6 (Debian 1:3.3.6-15)
but cell_defconfig and pseries_defconfig fail to build straight out.
This is what happens with pseries_defconfig:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CC arch/powerpc/kernel/asm-offsets.s
In file included from include/asm/mmu.h:7,
from include/asm/lppaca.h:32,
from include/asm/paca.h:20,
from include/asm/hw_irq.h:17,
from include/asm/system.h:9,
from include/linux/list.h:9,
from include/linux/signal.h:8,
from arch/powerpc/kernel/asm-offsets.c:16:
include/asm/mmu-hash64.h: In function `hpte_encode_r':
include/asm/mmu-hash64.h:216: warning: integer constant is too large for
"unsigned long" type
include/asm/mmu-hash64.h: In function `hpt_hash':
include/asm/mmu-hash64.h:231: warning: integer constant is too large for
"unsigned long" type
include/asm/mmu-hash64.h: In function `vsid_scramble':
include/asm/mmu-hash64.h:387: warning: right shift count >= width of type
include/asm/mmu-hash64.h:387: warning: left shift count >= width of type
include/asm/mmu-hash64.h:388: warning: right shift count >= width of type
include/asm/mmu-hash64.h:388: warning: left shift count >= width of type
include/asm/mmu-hash64.h: In function `get_kernel_vsid':
include/asm/mmu-hash64.h:395: error: `SID_SHIFT' undeclared (first use in
this function)
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-06 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 19:51 Christoph Lameter
2007-05-22 8:45 ` Pekka Enberg
2007-06-06 17:08 ` Andrew Morton
2007-06-06 18:36 ` Christoph Lameter
2007-06-06 20:11 ` Andrew Morton
2007-06-06 20:28 ` Christoph Lameter
2007-06-06 20:34 ` Andrew Morton
2007-06-06 20:41 ` Martin Bligh
2007-06-06 20:52 ` Christoph Lameter [this message]
2007-06-06 23:19 ` Andrew Morton
2007-06-06 23:50 ` Christoph Lameter
2007-06-07 0:01 ` Nish Aravamudan
2007-06-07 3:49 ` Christoph Lameter
2007-06-06 23:31 ` Nish Aravamudan
2007-06-07 7:40 ` Andy Whitcroft
2007-06-06 20:43 ` Christoph Lameter
2007-06-06 20:29 ` Nish Aravamudan
2007-06-07 7:48 ` Andy Whitcroft
2007-06-07 7:58 ` Andy Whitcroft
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.64.0706061349451.12665@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=penberg@cs.helsinki.fi \
/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