search for: size_

...72.57GB Disk_allocated: 25.10GB Disk_unallocated: 47.48GB Logical_size: 23.06GB Used: 11.01GB Free_(Estimated): 55.66GB (Max: 59.52GB, Min: 35.78GB) Data_to_disk_ratio: 92 % Details: Chunk_type Mode Size_(disk) Size_(logical) Used Data Single 21.01GB 21.01GB 10.34GB System DUP 80.00MB 40.00MB 4.00KB System Single 4.00MB 4.00MB 0.00 Metadata DUP 4.00GB 2.00GB 686.93MB Metadata Single 8...

...4d374fd0 (const string &const) corpus = error: summary string parsing error: { store_ = { = { small_ = {} *ml_ = (data_ = "��UH\x89�H�}�H\x8bE�]ÐUH\x89�H��H\x89}�H\x8bE�H\x89��~\xb4��\x90��UH\x89�SH\x83�H\x89}�H�u�H�E�H���\x9e���H\x8b\x18H\x8bE�H���O\xb4��H\x89ƿ\b", size_ = 0, capacity_ = 1441151880758558720)* } } } *(const string &const) needle = error: summary string parsing error: {* store_ = { = { small_ = {} ml_ = (data_ = "", size_ = 0, capacity_ = 1080863910568919040) } } } (facebook::biggrep::Options &) option...

...nst) corpus = error: summary string parsing error: { > store_ = { > = { > small_ = {} > *ml_ = (data_ = > "��UH\x89�H�}�H\x8bE�]ÐUH\x89�H��H\x89}�H\x8bE�H\x89��~\xb4��\x90��UH\x89�SH\x83�H\x89}�H�u�H�E�H���\x9e���H\x8b\x18H\x8bE�H���O\xb4��H\x89ƿ\b", > size_ = 0, capacity_ = 1441151880758558720)* > } > } > } > *(const string &const) needle = error: summary string parsing error: {* > store_ = { > = { > small_ = {} > ml_ = (data_ = "", size_ = 0, capacity_ = 1080863910568919040) > } &g...

...amp;)#1}*>() const+25> "\311\303UH\211\345H\211}\370H\213E\370]ÐUH\211\345H\203\354\020H\211}\370H\213E\370H\211\307\350~\264\312\377\220\311\303UH\211\345SH\203\354\030H\211}\350H\211u\340H\213E\340H\211\307\350\236\377\377\377H\213\030H\213E\350H\211\307\350O\264\312\377H\211ƿ\b", size_ = 0, capacity_ = 1441151880758558720}}}} Jeffrey On Sat, Mar 26, 2016 at 8:22 PM, David Blaikie <dblaikie at gmail.com> wrote: > If you're going to use clang built binaries with lldb, you'll want to pass > -fstandalone-debug - this is the default on platforms where...

We have a bad bug in udev if compiled with klibc. I seems that the needle string can't have a strlen of 1. This test case illustrates it: #include <stdio.h> #include <string.h> int main(int argc, char *argv[], char *envp[]) { char *hay = "a/b"; char *needle = "/"; if (memmem(hay, strlen(hay), needle, strlen(needle)) == NULL) printf("This uses the

...e considering two different possibilities for updating the bitcode wrapper specification. The first is to simply add a single 32bit wide field at the end of the existing bitcode wrapper format field. This would result in the new structure looking like this: [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, BitcodeVersion_{32}] All of the existing fields would keep their current meanings, and the new field BitcodeVersion is simply appended with the format described in the first paragraph. A second idea was to use the existing Version field in the bitcode wrapper format to store th...

...gt;() const+25> > "\311\303UH\211\345H\211}\370H\213E\370]ÐUH\211\345H\203\354\020H\211}\370H\213E\370H\211\307\350~\264\312\377\220\311\303UH\211\345SH\203\354\030H\211}\350H\211u\340H\213E\340H\211\307\350\236\377\377\377H\213\030H\213E\350H\211\307\350O\264\312\377H\211ƿ\b", > size_ = 0, > capacity_ = 1441151880758558720}}}} > > Jeffrey > > > > On Sat, Mar 26, 2016 at 8:22 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> If you're going to use clang built binaries with lldb, you'll want to >> pass -fstandalone-debu...

...e considering two different possibilities for updating the bitcode wrapper specification. The first is to simply add a single 32bit wide field at the end of the existing bitcode wrapper format field. This would result in the new structure looking like this: [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, BitcodeVersion_{32}] All of the existing fields would keep their current meanings, and the new field BitcodeVersion is simply appended with the format described in the first paragraph. A second idea was to use the existing Version field in the bitcode wrapper format to store th...

...pper specification. >> >> >> >> The first is to simply add a single 32bit wide field at the end of the >> existing bitcode wrapper format field. This would result in the new >> structure looking like this: >> >> [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, >> BitcodeVersion_{32}] >> >> All of the existing fields would keep their current meanings, and the new >> field BitcodeVersion is simply appended with the format described in the >> first paragraph. >> >> A second idea was to use the exi...

...>>> >>> >>> The first is to simply add a single 32bit wide field at the end of the >>> existing bitcode wrapper format field. This would result in the new >>> structure looking like this: >>> >>> [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, >>> BitcodeVersion_{32}] >>> >>> All of the existing fields would keep their current meanings, and the >>> new field BitcodeVersion is simply appended with the format described in >>> the first paragraph. >>> >>> A se...

Building on Solaris 8 with Sun's compiler, I get the following error. Would you fix this? Using gcc is not really a good option for me. /opt/forte8/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/csw/inclu\de -fast -xarch=v8 -I/opt/csw/include -c buffer.c "buffer.c", line 159: void function cannot return value "buffer.c", line 205: void function cannot return

...or updating the bitcode wrapper > specification. > > > > The first is to simply add a single 32bit wide field at the end of the > existing bitcode wrapper format field. This would result in the new > structure looking like this: > > [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, > BitcodeVersion_{32}] > > All of the existing fields would keep their current meanings, and the new > field BitcodeVersion is simply appended with the format described in the > first paragraph. > > A second idea was to use the existing Version field in the b...

I want to use the plot(model) function to generate Tukey-anscomb and Q-Q plots of a lm(). I manage to change all labels but the main one which apparently is neither main or sub. So far I have tried as par setting: cex (changes symbol size within the plot), cex.main (no effect), cex.sub (no effect) cex.lab (changes label size), cex.axis (changes axis label size). What I would like to change is the

Thanks a lot for your reply! You guessed it right though - mailing lists, various blogs, documentation, videos and even source code at this point. Changing some off the options does make performance slightly better, but nothing particularly groundbreaking. So, if I understand you correctly, no one has yet managed to get acceptable performance (relative to underlying hardware capabilities) with

Hello all: This seires is an update of last version of multiqueue support to add multiqueue capability to both tap and virtio-net. Some kinds of tap backends has (macvatp in linux) or would (tap) support multiqueue. In such kind of tap backend, each file descriptor of a tap is a qeueu and ioctls were prodived to attach an exist tap file descriptor to the tun/tap device. So the patch let qemu to

Hello all: This seires is an update of last version of multiqueue support to add multiqueue capability to both tap and virtio-net. Some kinds of tap backends has (macvatp in linux) or would (tap) support multiqueue. In such kind of tap backend, each file descriptor of a tap is a qeueu and ioctls were prodived to attach an exist tap file descriptor to the tun/tap device. So the patch let qemu to

Hello all: This seires is an update of last version of multiqueue support to add multiqueue capability to both tap and virtio-net. Some kinds of tap backends has (macvatp in linux) or would (tap) support multiqueue. In such kind of tap backend, each file descriptor of a tap is a qeueu and ioctls were prodived to attach an exist tap file descriptor to the tun/tap device. So the patch let qemu to

Hello all: This seires is an update of last version of multiqueue support to add multiqueue capability to both tap and virtio-net. Some kinds of tap backends has (macvatp in linux) or would (tap) support multiqueue. In such kind of tap backend, each file descriptor of a tap is a qeueu and ioctls were prodived to attach an exist tap file descriptor to the tun/tap device. So the patch let qemu to

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.