Displaying 3 results from an estimated 3 matches for "1141808".
Did you mean:
114108
2005 Nov 22
2
RE: __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
>From: Rusty Russell
>Sent: 2005年11月21日 12:53
>Hi all,
>
> While browsing the code, I noticed this in xmalloc.c:
>
>#ifndef __ia64__
> BUG_ON(align > SMP_CACHE_BYTES);
>#endif
>
> This is clearly wrong: due to header alignment we cannot give you a
>greater alignment than SMP_CACHE_BYTES. Overriding this will cause the
>allocation to succeed, but not
2005 Nov 23
0
RE: __ia64__ ifdef in xmalloc.c: "Fix ar.unat handling forfast paths"
....
Understand. ;-)
>
>How much is this trick saving us? Static size of data area in
>vmlinux doesn''t change very much as SMP_CACHE_BYTES is varied:
>
> text data bss dec hex filename
>8677481 1139704 1206357 11023542 a834b6 vmlinux-8
>8677417 1141808 1206397 11025622 a83cd6 vmlinux-16
>8677417 1146000 1206477 11029894 a84d86 vmlinux-32
>8677353 1146256 1206573 11030182 a84ea6 vmlinux-64
>8677353 1163152 1207085 11047590 a892a6 vmlinux-128
>
>I''m not sure how to evaluate dynamic behavior (a...
2015 Sep 29
2
Building clang in llvm-3.7 on Linux with RT support enabled
Hi Chris and Alex,
Many thanks for these replies.
> I dug a little deeper into the history here. It looks like the blocks runtime hasn’t built in the CMake build system in a long time, and I don’t think it has ever been supported in the autoconf system.
>
> Support for building it with CMake was removed in April 2012 along with the old CMake build system (r154059) because it was