search for: holing

On Aug 31, 2012, at 3:13 PM, Chris Lattner <clattner at apple.com> wrote: > On Aug 30, 2012, at 1:34 PM, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote: >> On 8/22/2012 3:15 PM, Dan Gohman wrote: >>> Here's an example showing the basic problem: >>> >>> struct bar { >>> char x; >>> float y; >>> double z;

[originally reported for ZFS on FreeBSD but Pawel Jakub Dawid says this problem also exists on Solaris hence this email.] Summary: on ZFS, overhead for reading a hole seems far worse than actual reading from a disk. Small buffers are used to make this overhead more visible. I ran the following script on both ZFS and UF2 filesystems. [Note that on FreeBSD cat uses a 4k buffer and md5 uses a 1k

On Aug 30, 2012, at 1:34 PM, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote: > On 8/22/2012 3:15 PM, Dan Gohman wrote: >> Here's an example showing the basic problem: >> >> struct bar { >> char x; >> float y; >> double z; >> }; >> void copy_bar(struct bar *a, struct bar *b) { >> *a = *b; >> } >>

<moving this to llvmdev now that the lists are back up!> On Aug 23, 2012, at 4:37 PM, Dan Gohman <gohman at apple.com> wrote: > On Aug 23, 2012, at 4:05 PM, Chris Lattner <clattner at apple.com> wrote: >> On Aug 23, 2012, at 3:59 PM, Dan Gohman <gohman at apple.com> wrote: >>> On Aug 23, 2012, at 3:31 PM, Chris Lattner <clattner at apple.com> wrote:

Instead of printing something like ‘type=0’ or ‘type=3’, this changes the output to show the hole and zero flags separately. For example: $ ./nbdkit -U - --filter=log sh - logfile=/dev/stdout \ --run 'qemu-img map $nbd' <<'EOF' case "$1" in get_size) echo 1M ;; pread) dd if=/dev/zero count=$3 iflag=count_bytes ;; can_extents) exit 0 ;;

Hi. I've tried to create a polygon with one hole by gpclib using following example script. holepoly <- read.polyfile(system.file("poly-ex/hole-poly.txt", package ="gpclib"), nohole = FALSE) area.poly(holepoly) plot(holepoly,poly.args=list(col="red",border="blue")) And I noticed plot function couldn't draw polygons with holes correctly.

I have obtained shapefiles for Indian states from here: http://www.maptell.com/index.php?option=com_remository&Itemid=159&func=fileinfo&filecatid=115&parent=category Problem: I want to extract centroid coordinates for each State, but there is some coding problem with the shapefiles that prevents this. #Code: #After extracting the shapefiles from the india_state.zip file, then:

Hi everyone, At EuroLLVM, Chandler and I chatted about the design for a potential TBAA sanitizer. Here's my attempt to summarize: C/C++ have type-based aliasing rules, and LLVM's optimizer can exploit these given TBAA metadata added by Clang. Roughly, a pointer of given type cannot be used to access an object of a different type (with, of course, certain exceptions). Unfortunately,

Allow compile time creation of a hole at the high end of linear address space. This makes accomodating a hypervisor a much more tractable problem by giving it ample playground to live in. Currently, the hole size is fixed at config time; I have experimented with dynamically sized holes, and have a later patch that developes this potential, but it becomes much more useful once the exact

Allow compile time creation of a hole at the high end of linear address space. This makes accomodating a hypervisor a much more tractable problem by giving it ample playground to live in. Currently, the hole size is fixed at config time; I have experimented with dynamically sized holes, and have a later patch that developes this potential, but it becomes much more useful once the exact

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

I have a partly damaged CD, from which I extracted 192Kb/s Vorbis files a while ago (before it got damaged) and I'd like to get FLAC files. `cdparanoia' extracted most of the data from the CD, but there are some holes due to the damages. How could I fill those holes in my FLAC files using the Vorbis files? Stefan

I have a partly damaged CD, from which I extracted 192Kb/s Vorbis files a while ago (before it got damaged) and I'd like to get FLAC files. `cdparanoia' extracted most of the data from the CD, but there are some holes due to the damages. How could I fill those holes in my FLAC files using the Vorbis files? Stefan

I have a partly damaged CD, from which I extracted 192Kb/s Vorbis files a while ago (before it got damaged) and I'd like to get FLAC files. `cdparanoia' extracted most of the data from the CD, but there are some holes due to the damages. How could I fill those holes in my FLAC files using the Vorbis files? Stefan

On 04/10/2017 09:55 AM, Andrey Bokhanko wrote: > Hi Hal, > > I wonder how your solution will handle the following? > > struct { > int s1_f1; > float s1_f2; > int s1_f3; > float s1_f4; > } S1; > > struct { > int s2_f1; > float s2_f2; > int *s2_f3; // to add some interest, suppose that sizeof(int) == > sizeof(int *) > float s2_f4;

Hi,all I have tried to passthrough GPU card(Nvidia quadro 4000) on the latest Xen unstable version (QEMU is using Qemu-upsteam-unstable, not traditional Qemu). This issue as below: Windows7 64-bit guest will blue screen when GPU passthrough configure 4g memory,blue screen code is 50, and SUSE 11 64-bit guest will always stay at the grub screen. I noticed that it will relocate RAM that

On 04/11/2017 03:46 AM, Andrey Bokhanko wrote: > Hal, > > To clarify, my example meant to illustrate that for memory references > to structures' fields you have to keep a user-defined type, even for > one byte accesses. C++ allows references to "initial member sequence" > using pointers to structures of different types. And yes, there are > programs in the

On 10/13/2017 10:19 AM, Anand Buddhdev wrote: > .. > Stop trying to force a square peg into a round hole. Whee, I just _know_ I'm going to be positively skewered (and maybe even plonked!) for this.... but, hey, it's Friday, and this post is meant to be a bit funny.? So lighten up, and enjoy a short read. obHumor: I actually have a piece of furniture (a small table) with square

the data in holes is actually not zeros as there might be a parent image having other data. Properly reporting (non-)zero hole extents allows clients to have information about whether the data in the image is unallocated, but the read will return zero blocks (HOLE+ZERO) or whether the data is just not in this later of the image (only HOLE). Signed-off-by: Martin Kletzander

Keir, Here''s a first patch to address the issue with rolling over to guest-physical address 0x00000000 when assigning address regions to PCI BARs during HVM boot. For now, this: - Makes the hole bigger: 0xC0000000-0xF5000000. This might be overkill...but it should only matter for 32-bit guest OSes assigned more than 3GB of RAM. - Prevents addresses from above 0xF50000000 from