search for: 100541

In SelectionDAG, what's the difference between getConstant and getTargetConstant? One creates a node with opcode Constant and the other with TargetConstant. What's the semantic difference? In X86ISelLowering I need to create a constant vector and put it in memory so I can reference it as an operand. I don't see any examples of doing this. Is it possible? If so, what's the

I added some comments here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100426/100541.html To put a constant in memory, you should use a constant pool entry, and the constant pool infrastructure. Dan On Apr 29, 2010, at 8:23 AM, David Greene wrote: > In SelectionDAG, what's the difference between getConstant and > getTargetConstant? One creates a node with opcode Cons...

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-x wait" option: [ from

While attempting to install snv_85 as a domU, Debian etch as the dom0, the kernel panics before the rest of the system starts to boot. Currently I''m using the sid releases of xen 3.2 found in Debian sid. I stopped using 3.0.3, as it appears I''m unable to use a ramdisk setting. # dmesg | grep -i mem ... Memory: 1903728k/1949252k available (1623k kernel code, 36208k reserved,

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =