search for: msg00479

We''ve run into an issue with an 8 node x3950 where xm info is showing only 6 nodes. I''ve traced the problem to the clip_to_limit function in arch/x86/e820.c. #ifdef __x86_64__ clip_to_limit((uint64_t)(MACH2PHYS_COMPAT_VIRT_END - __HYPERVISOR_COMPAT_VIRT_START) << 10, "Only the first %u GB of the physical memory map

Hi, I'm trying to build llvm 3.4 on one of our Cray systems, note: 3.2 builds fine. The following error occurs, it looks like a system header, intended for C only judging by the fact that there's a variable named "new", is being used in one of llvm's C++ source files. Can anyone suggest a workaround? I do not have root on this system nor is it likely that I can convince

Can anybody help me with this : ? I first generated rsa key with this : ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key then I went on to generate the DSA key too....(just incase my SSHD does not like RSA). ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key and then I ran root at 00_00_09_PECA_NP1:/usr/bin# sshd -d -d -d -d -d -d -d -d -d debug3: RNG is ready, skipping seeding debug2:

Having read through Stackless Python's web pages a bit: 1. They're doing pretty much what I'd like to do, except that I don't want to be tied to a particular language and I'd like to be able to use the stack. (Also, stack use is inescapable with LLVM, as far as I can tell). 2. We should be able to support "hard switching" in Stackless Python by adding a

On the other hand, stack manipulation really ought to be handled by the target, since only the target knows the details of how the stack is laid out to begin with. Also, if we have stack manipulation calls in the IR, optimization quickly becomes very difficult. Unless we just allow optimizers to ignore the stack manipulations and assume they're doing the "right" thing. On the

...the stack (unless a function pointer > to malloc or its equivalent is passed in from the IR). In gcc's split-stacks (http://gcc.gnu.org/ml/gcc/2009-02/msg00429.html; I got the name wrong earlier), Ian planned to call a known global name to allocate memory (http://gcc.gnu.org/ml/gcc/2009-02/msg00479.html). I'm not sure what he actually wound up doing on the gccgo branch. LLVM could also put the allocation/deallocation functions into the context, although it'd probably be better to just follow gcc. >> The way they accomplish that now is by >> copying the entire stack to the...

...n pointer >> to malloc or its equivalent is passed in from the IR). > > In gcc's split-stacks > (http://gcc.gnu.org/ml/gcc/2009-02/msg00429.html; I got the name wrong > earlier), Ian planned to call a known global name to allocate memory > (http://gcc.gnu.org/ml/gcc/2009-02/msg00479.html). I'm not sure what > he actually wound up doing on the gccgo branch. LLVM could also put > the allocation/deallocation functions into the context, although it'd > probably be better to just follow gcc. > >>> The way they accomplish that now is by >>> copy...