Date: Sat, 12 Jun 2004 21:20:24 -0700
From: Paul Jackson <pj@sgi.com>
To: Clemens Schwaighofer <schwaigl@eunet.at>
Cc: gullevek@gullevek.org, linux-kernel@vger.kernel.org, cs@tequila.co.jp
Subject: Re: compile error with 2.6.7-rc3-mm1
Message-Id: <20040612212024.0bbec683.pj@sgi.com>
In-Reply-To: <40CBD251.4000601@eunet.at>
References: <40C9AF48.2040807@gullevek.org>
	<20040611062829.574db94f.pj@sgi.com>
	<40CA6835.2070405@eunet.at>
	<20040612034430.72a8207e.pj@sgi.com>
	<40CBC809.3000102@eunet.at>
	<20040612204207.0136b76f.pj@sgi.com>
	<40CBD251.4000601@eunet.at>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1408
Lines: 43

> | preprocessor output, to see if the (cpumask_t) cast is present.
> |
> 
> yeah I have the cputmask_t here:

No - look to see if the __cast__ is there, the (cpumask_t) term
that was needed in the define of CPU_MASK_NONE:

#define CPU_MASK_NONE                                                   \
((cpumask_t){ {                                                         \
        [0 ... BITS_TO_LONGS(NR_CPUS)-1] =  0UL                         \
} })

This would be on the preprocessor code that is generated from line
1137 of drivers/perfctr/x86.c, where the error is generated.   This is
the source line that looks like:

	old_mask = perfctr_cpus_forbidden_mask;

The preprocessor output from this line in the x86.i file will look
something like this, hopefully:

   Good:

	old_mask = ((cpumask_t){ { [0 ... (((8)+32 -1)/32)-1] = 0UL } });

Not like this:

   Bad:

	old_mask = { { [0 ... (((8)+32 -1)/32)-1] = 0UL } };

(the '8' varies with your NR_CPUS configuration).

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/