search for: l836

...bguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsLFMzZI skippy at DaneelOlivaw:~/tmp/bin$ /build/buildd/qemu-kvm-1.2.0+noroms/nbd.c:nbd_trip():L835: From: 18446744073709551104, Len: 0, Size: 20003880960, Offset: 77824 /build/buildd/qemu-kvm-1.2.0+noroms/nbd.c:nbd_trip():L836: requested operation past EOF--bad client? /build/buildd/qemu-kvm-1.2.0+noroms/nbd.c:nbd_receive_request():L516: read failed So I peppered some fprintfs in launch-appliance.c to try and narrow down the problem. Just below the comment: * does not mean the daemon is up until we read the * GUE...

> On Feb 29, 2016, at 11:28 PM, Chandler Carruth <chandlerc at google.com> wrote: > > I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. Mmmmm, thinking more about it, yes we could compile the IR two times and use the unoptimized one as a reference. However, right now the tests are only running llc, so the

I really don't understand this. Why is a C++ reference useful? Instead, we have an IR reference: the unoptimized IR. I think it pretty important to not phrase everything in terms of C or C++ or Clang... =/ What if there are IR constructs that simply cannot be produced by C++? We're adding lots of those for managed languages. If there is a practical concern with having IR-based test