search for: space

...etected RPM version 4.11 supermin: package handler: fedora/rpm supermin: acquiring lock on /var/tmp/.guestfs-1000/lock supermin: build: /usr/lib64/guestfs/supermin.d supermin: build: visiting /usr/lib64/guestfs/supermin.d/base.tar.gz type gzip base image (tar) tar: ./etc/tcsd.conf: Cannot write: No space left on device tar: ./etc/aliases: Cannot write: No space left on device tar: ./etc/bashrc: Cannot write: No space left on device tar: ./etc/csh.cshrc: Cannot write: No space left on device tar: ./etc/csh.login: Cannot write: No space left on device tar: ./etc/filesystems: Cannot write: No space le...

...? Lines2<-Lines1[Lines1!=""] library(stringr) ?str_count(Lines2, " ") # [1] 7 7 7 7 6 7 7 7 7 7 6 6 7 7 7 7 6 7 7 7 7 7 6 6 Lines2[str_count(Lines2," ")==7]<- str_replace(Lines2[str_count(Lines2," ")==7],"\\s+","???? ") #reduced 2 spaces ?Lines2[str_count(Lines2," ")==6]<- str_replace(Lines2[str_count(Lines2," ")==6],"\\s+","??? ") #reduced 2 spaces ?str_count(Lines2," ") # [1] 5 5 5 5 4 5 5 5 5 5 4 4 5 5 5 5 4 5 5 5 5 5 4 4 substr(Lines2[substr(Lines2,6,6)==0|substr(Lines2,9,9...

Hi Rich, I'm not sure how far this helps as it mostly says 'No space left on device', but here's the output of the command you asked me to run: ➜ tmp /usr/bin/supermin --build -v -v -v --copy-kernel -f ext2 --host-cpu x86_64 /usr/lib64/guestfs/supermin.d -o /tmp/appliance.d supermin: version: 5.1.9 supermin: rpm: detected RPM version 4.11 supermin: packa...

...istrator After this my krb5.keytab file is filled with the following: root at ubuntu100432:~# klist -kte Keytab name: WRFILE:/etc/krb5.keytab KVNO Timestamp Principal ---- ----------------- -------------------------------------------------------- 2 02/13/12 09:34:59 host/ubuntu100432.a.space.corp at A.SPACE.CORP (DES cbc mode with CRC-32) 2 02/13/12 09:34:59 host/ubuntu100432.a.space.corp at A.SPACE.CORP (DES cbc mode with RSA-MD5) 2 02/13/12 09:34:59 host/ubuntu100432.a.space.corp at A.SPACE.CORP (ArcFour with HMAC/md5) 2 02/13/12 09:34:59 host/ubuntu100432 at A.SPACE.CORP (D...

On Fri, Feb 25, 2011 at 02:55:33PM -0500, Ken Dyck wrote: > The address space mechanism is used by some code generators to > differentiate between physical memory spaces. The PIC16 code generator > uses address spaces 0 and 1 to select between its RAM and ROM spaces. > And X86 uses address space 256 for GS and 257 for FS. In the back end > for a dual-harvard DSP...

...001: hiddev0,hidraw0: USB HID v1.00 Device [Yubico Yubico Gnubby (gnubby1)] on usb-0000:00:14.0-2/input0 [ 9.784456] Console: switching to colour frame buffer device 240x67 [ 9.816297] i915 0000:00:02.0: fb0: i915drmfb frame buffer device [ 25.087400] thunderbolt 0000:06:00.0: saving config space at offset 0x0 (reading 0x15eb8086) [ 25.087414] thunderbolt 0000:06:00.0: saving config space at offset 0x4 (reading 0x100406) [ 25.087419] thunderbolt 0000:06:00.0: saving config space at offset 0x8 (reading 0x8800006) [ 25.087424] thunderbolt 0000:06:00.0: saving config space at offset 0xc...

...love to hear peoples thoughts on how to best fix it. Background As you may or may not know, I maintain the in-tree AVR backend, which also happens to be (to the best of my knowledge) the first in-tree backend for a Harvard architecture. In this architecture, code lives inside the ‘program memory’ space (numbered 1), whereas data lives inside RAM “data space”, which corresponds to the default address space 0. This is important because loads/stores use different instruction/pointer formats depending on the address space used, and so we need correct address space information available to the backend...

...new rules files and patches are inline. The following patch is for violations.ignore.d: --- logcheck-postfix.orig 2004-06-21 20:11:14.000000000 +0100 +++ logcheck-postfix 2004-06-21 20:10:32.000000000 +0100 @@ -1,4 +1,8 @@ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: warning: [^[:space:]]+: hostname [^[:space:]]+ verification failed: Host not found$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: [[:alnum:]]+: reject: RCPT from [^[:space:]]+: [0-9]+ Client host rejected: cannot find your hostname, [^[:space:]]+; from=[^[:space:]]+ to=[^[:space:]]+ proto=(ESMTP|SMTP)...

On 08/07/2015 12:22 PM, Daniel Berlin via llvm-dev wrote: > Sorry to be pedantic, but i think it's important to make sure we are > all on the same page that backends can't change the aliasing behavior > of the default address space, only the aliasing behavior of the other > address spaces. Are you saying that we can't say address space 0 doesn't alias other address spaces? In this case we really need to fix LLVM's concept of default address space because this is highly problematic for us. We're constrain...

> [Micah Villmow] The backends won't understand your address space mapping. The backends should expose their address spaces that they support, their sizes and their overall semantics. It should be documented just like the calling convention is documented. It is then the job of the frontend to map whatever source language address spaces are used onto the correct ad...

...rote: >> >> IMHO this information should be a plus that could be *safely* ignored when not necessary and used where it can provide an improvement in optimizations. This does not necessary mean the the middle-end (and the back-ends) must be aware of the semantic of these logical address spaces, it would be enough just to distinguish between two logically different address spaces. >> The first application I see is alias analysis: for targets that do not have different physical address spaces (e.g. X86), meaning that in the IR the 'addrspace' modifier *should* not be presen...

...2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> wrote: >> >>> On 08/08/2013 02:02 AM, Justin Holewinski wrote: >>>> This worries me a bit. This would introduce language-specific >>>> processing into SelectionDAG. OpenCL maps address spaces one way, other >>>> languages map them in other ways. Currently, it is the job of the >>>> front-end to map pointers into the correct address space for the target >>>> (hence the address space map in clang). With (my understanding of) this >>>> pro...

On Thu, Oct 13, 2011 at 06:59:47PM +0000, Villmow, Micah wrote: > Justin, > Out of these options, I would take the metadata approach for AA support. > > This doesn't solve the problem of different frontend/backends choosing different > address space representations for the same language, but is the correct > approach for providing extra information to the optimizations. > > The issue about memory spaces in general is a little different. For example, based on > the code you posted below, address space 0(default) is global in CUDA,...

...008 at 5:08 AM, Matthijs Kooijman <matthijs at stdin.nl> wrote: > Now, we are using a function which reads a value from one of these memories > and does some processing. Since we want to execute this function for multiple > memories, we make it accept a pointer in the generic address space (ie, no > address space attribute): > > void do_stuff(char* mem); The "generic address space" you're referring to is really just address space 0, at least in the current implementation. Assuming alternate address spaces are actually separate, passing a pointer from a...

Hi all, I'm currently struggling a bit with some problems regarding address spaces and (implicit) casts. I'll explain some context first and then proceed to the actual question I'd like to have answered. In our target platform, we have a number of distinctly different memory banks. To access these from our C code, we declare a global array for each memory, with the addr...

On Mon, Feb 28, 2011 at 4:41 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > The more I think about it, the more I become uncomfortable with the > concept of language-specific address spaces in LLVM.  These are the > main issues I see with language-specific address spaces: ... > Instead of language-specific address spaces, each target should > concentrate on exposing all of its address spaces as target-specific > address spaces, and frontends should use a language ->...

...06:59:47PM +0000, Villmow, Micah wrote: > > > Justin, > > > Out of these options, I would take the metadata approach for AA support. > > > > > > This doesn't solve the problem of different frontend/backends choosing > > different > > > address space representations for the same language, but is the correct > > > approach for providing extra information to the optimizations. > > > > > > The issue about memory spaces in general is a little different. For > > example, based on > > > the code you posted be...

On Tue, Mar 1, 2011 at 4:06 PM, David Neto wrote: > On Mon, Feb 28, 2011 at 4:41 PM, Peter Collingbourne wrote: >> >> The more I think about it, the more I become uncomfortable with the >> concept of language-specific address spaces in LLVM.  These are the >> main issues I see with language-specific address spaces: > > ... > >> Instead of language-specific address spaces, each target should >> concentrate on exposing all of its address spaces as target-specific >> address spaces, and frontends...

...: > > > On Aug 7, 2013, at 5:12 PM, Michele Scandale <michele.scandale at gmail.com> > wrote: > > On 08/08/2013 02:02 AM, Justin Holewinski wrote: > > This worries me a bit. This would introduce language-specific > processing into SelectionDAG. OpenCL maps address spaces one way, other > languages map them in other ways. Currently, it is the job of the > front-end to map pointers into the correct address space for the target > (hence the address space map in clang). With (my understanding of) this > proposal, there would be a pre-defined set of langu...

...draw0: USB HID v1.00 Device [Yubico Yubico Gnubby (gnubby1)] on usb-0000:00:14.0-2/input0 > [ 9.784456] Console: switching to colour frame buffer device 240x67 > [ 9.816297] i915 0000:00:02.0: fb0: i915drmfb frame buffer device > [ 25.087400] thunderbolt 0000:06:00.0: saving config space at offset 0x0 (reading 0x15eb8086) > [ 25.087414] thunderbolt 0000:06:00.0: saving config space at offset 0x4 (reading 0x100406) > [ 25.087419] thunderbolt 0000:06:00.0: saving config space at offset 0x8 (reading 0x8800006) > [ 25.087424] thunderbolt 0000:06:00.0: saving config space...