From: "Jürgen Groß" <jgross@suse.com>
To: Jan-Simon Moeller <dl9pf@gmx.de>, xen-devel@lists.xenproject.org
Subject: Re: Question about arch/x86/xen/mmu.c
Date: Fri, 05 Dec 2014 05:47:49 +0100 [thread overview]
Message-ID: <548138F5.30405@suse.com> (raw)
In-Reply-To: <1727998.ort8X4yb3k@aragorn.auenland.lan>
On 12/04/2014 10:30 PM, Jan-Simon Moeller wrote:
> Hi !
>
> My name is Jan-Simon Moeller and I'm looking into compiling the kernel with
> LLVM/Clang (see llvm.linuxfoundation.org) .
>
> Right now we face this issue when compiling with clang:
>
> CC arch/x86/xen/mmu.o
> arch/x86/xen/mmu.c:1343:18: error: fields must have a constant size:
> 'variable length array in structure' extension will never be
> supported
> DECLARE_BITMAP(mask, num_processors);
> ^
> include/linux/types.h:10:16: note: expanded from macro 'DECLARE_BITMAP'
> unsigned long name[BITS_TO_LONGS(bits)]
> ^
> 1 error generated.
>
>
> Question to the experts: why can't we just use NR_CPUS and be done with it ?
> NR_CPUS will be setup by CONFIG_NR_CPUS and thus static.
> ( e.g. arch/x86/configs/x86_64_defconfig:CONFIG_NR_CPUS=64 )
This would expand the structure on kernels configured for many cpus
(e.g. 4096) but running on a smaller machine dramatically.
Juergen
prev parent reply other threads:[~2014-12-05 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:30 Question about arch/x86/xen/mmu.c Jan-Simon Moeller
2014-12-05 4:47 ` Jürgen Groß [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=548138F5.30405@suse.com \
--to=jgross@suse.com \
--cc=dl9pf@gmx.de \
--cc=xen-devel@lists.xenproject.org \
/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.