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
Date: Sat, 12 Jun 2004 21:20:24 -0700 [thread overview]
Message-ID: <20040612212024.0bbec683.pj@sgi.com> (raw)
In-Reply-To: <40CBD251.4000601@eunet.at>
> | 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
next prev parent reply other threads:[~2004-06-13 4:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 13:10 compile error with 2.6.7-rc3-mm1 Clemens Schwaighofer
2004-06-11 13:28 ` Paul Jackson
2004-06-12 2:19 ` Clemens Schwaighofer
2004-06-12 10:44 ` Paul Jackson
2004-06-13 3:20 ` Clemens Schwaighofer
2004-06-13 3:42 ` Paul Jackson
2004-06-13 4:04 ` Clemens Schwaighofer
2004-06-13 4:20 ` Paul Jackson [this message]
2004-06-13 6:22 ` Clemens Schwaighofer
2004-06-13 6:39 ` Paul Jackson
2004-06-13 6:45 ` Paul Jackson
2004-06-13 6:08 ` Sam Ravnborg
2004-06-13 6:03 ` Paul Jackson
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=20040612212024.0bbec683.pj@sgi.com \
--to=pj@sgi.com \
--cc=cs@tequila.co.jp \
--cc=gullevek@gullevek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwaigl@eunet.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.