similar to: i386 hypervisor seeing only ~16G RAM, amd64 required?

On Wed, Jun 25, 2014 at 3:30 PM, John Criswell <criswell at illinois.edu> wrote: > On 6/25/14, 5:15 PM, Vadim Chugunov wrote: > > In a recent review via Phabricator, I was receiving bounce notifications for > mail being sent to llvm-commits because of "Too many recipients to the > message", even though I am a subscriber. I wonder how common is that. > > >

Hey folks, If I've got some code that I can compile using clang, that depends on a certain endianness, can I generate bitcode that will have the code operate correctly, even if run on machines of the the opposite endianness? If not, what're we talking about in specific work that'd be needed? Thanks, - Lally

What exactly is different between the 32 and 64-bit version of CentOS 4.2? The kernel (drivers, file system, etc.) is probably compiled to support 64-bit and probably glibc. What're some important differences between the 32 and 64-bit version? I'm just trying to get a deeper understanding. Thanks in advance for any help. FongVang

Processing commands for control@bugs.debian.org: > reassign 387238 xen-hypervisor-3.0.2-1-i386 Bug#387238: xen-hypervisor: Xen hypervisor reboots when scrubbing ram message is reached: confirmed on AMD64 and i386 Warning: Unknown package 'xen-hypervisor' Bug reassigned from package `xen-hypervisor' to `xen-hypervisor-3.0.2-1-i386'. > -- Stopping processing here. Please

Your message dated Wed, 13 Sep 2006 10:34:57 +0200 with message-id <20060913083457.GA11942@wavehammer.waldi.eu.org> and subject line fixed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB:

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

Hello, the need here is to have a single LLVMContext used for multiple compilations. You make a good point about that by the way. If there are outstanding users cleaning the context under their seats might still pose a risk to them, and in that case deleting + newing a new LLVMContextImpl might actually not be very different. Marcello 2014-06-24 17:14 GMT+01:00 David Blaikie <dblaikie at

I have seen the "Too many recipients to the message" several times. A limit of 10 includes the patch author and the list leaving just 8 subscribers/reviewers is way too low. Given that these e-mails can be sent only by a Phab. user I'm not sure that spam is a problem at all: A potential spammer would first have to subscribe to Phab. then create a proper diff,... far easier just to

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does

Something like, keeping the compiler alive for a many compilation sessions, using the same LLVMContext, but without the problem of accumulating data in the LLVMContext that would slowly fill up the memory. This as much I can enter into details that I can :/ Probably this is also a quite common use case scenario too. Marcello 2014-06-24 18:52 GMT+01:00 Eric Christopher <echristo at

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.8 Severity: critical We're seeing this too on 4.0.1-5.8, and it's causing major problems. Xen on Debian Squeeze is basically unusable with the latest packages. Is a fixed package in sight? Thanks, Ward. -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

Hey guys, This is kind of odd, so I wanted to do a sanity check. I mounted an NFS share like so: [root at web1:~] #mount -t nfs nfs1.jokefire.com:/home /mnt/home Seemed to go ok. Then I took a look at the output of df -h and didn't see it! [root at web1:~] #df -h Filesystem Size Used Avail Use% Mounted on /dev/vda 40G 24G 14G 64% / devtmpfs

> On 2015 Apr 14, at 21:46, David Blaikie <dblaikie at gmail.com> wrote: > > On Tue, Apr 14, 2015 at 9:33 PM, Duncan P. N. Exon Smith > <dexonsmith at apple.com> wrote: >> >> `Function` definitions should support `MDNode` attachments, with a >> similar syntax to instructions: >> >> define void @foo() nounwind !attach !0 { >>

> On 2015 Apr 15, at 10:06, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Tue, Apr 14, 2015 at 10:59 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > > > On 2015 Apr 14, at 21:46, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Tue, Apr 14, 2015 at 9:33 PM, Duncan P. N. Exon Smith > > <dexonsmith at

after upgrading to 3.0.2+hg9697-2 I experience the same problem! I switched to xen-hypervisor-3.0-amd64, but it shows the same effect! AMD Athlon64 3800+ machine - was running fine with 3.0.2+hg9697-1 until last saturday... MfG Sebastian Rieger

&gt; If possible it might be interesting to first try the 4.6 hypervisor in&gt; Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just install&gt; on Jessie with no issues since it has no dependencies and you don't need&gt; the userspace tools just to check if it boots.Hey there,I can confirm the issue with new Intel i7-6700 Quad-Core Skylake CPUs and I'm also

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze sid Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: critical Justification: breaks the whole system Dear Maintainer, -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8,

Hi All, We've been working on enhancing LLVM's instrumentation based profiling by adding indirect call target profiling support. Our goal is to add instrumentation around indirect call sites, so that we may track the frequently taken target addresses and their call frequencies. The acquired data has uses in optimization of indirect function call heavy applications. Our initial findings

Dear Everyone, I am running FreeBSD 9.1-BETA1 amd64 on ZFS in KVM on Gentoo Linux on ZFS. The root pool uses ashift=13 and is on a single disk. The kernel fails to mount the root filesystem if the system has more than 3584MB of RAM. I did a manual binary search to try to find the exact upper limit, but stopped when I tried 3648MB. FreeBSD 9.0-RELEASE works perfectly. Yours truly, Richard Yao