search for: undefinit

...impossible. What did I miss? My other question is about the permanent flags being displayed upon selecting a mailbox. I'm trying to understand why unused keywords are still showing up in there. Is there a way to force the definitive removal of a keyword from a mailbox? are old keywords kept undefinitely? Thanks in advance, Arnaud -- Arnaud Ab?lard jabber: arnaud.abelard at univ-nantes.fr / twitter: ArnY Administrateur Syst?me DSI Universit? de Nantes -

.... autorun DONE. Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root SElinux: Disabled at runtime SElinux: Unregistering netfilter hooks Then, it hangs here undefinitely. Here is my menu.lst grub file on the backup disk I want to boot from: default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.106.unsupported) root (hd0,0) kernel /vmlinuz-2.6.9-11.106.unsupported root=/dev/hda3 initrd /initrd-2.6.9...

...keLinux 8.1 on 4 different machines and a notebook. I have updated the system with the first UpDate CD. My problem is that when I start a Win32 application, say Word97, Wincp, Winzip and other private applications, nothing happens. It means that after complaining about non existant fonts, wine run undefinitly, and winreal take about 95% of the processor time. Nothing crash, nothing appearing on the screen.The only functionning application are some games like sol.exe. I have tried it on different machine (PII from 450 up to 800Mhz and AMD 1700+), the result is the same. With Mandrake 8.0 and my privat...

...python API with the same rate of success than virt-manager. # virsh version Compiled against library: libvir 0.8.3 Using library: libvir 0.8.3 Using API: Xen 3.0.1 Running hypervisor: Xen 3.2.0 The goal is to have the migration done in only one call, including a definition in the remote xend and undefinition from the source, which requires the VIR_MIGRATE_PERSIST_DEST and VIR_MIGRATE_UNDEFINE_SOURCE flags. Here's the code doing the migration: ---------- flags = (libvirt.VIR_MIGRATE_LIVE ^ libvirt.VIR_MIGRATE_PERSIST_DEST ^ libvirt.VIR_MIGRATE_UNDEFINE_SOURCE) uri = 'xenmigr...

...adata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIFileInclude" nodes. DIMacro will contain: * type (definition/undefinition). * line number (interger). * name (null terminated string). * replacement value (null terminated string - optional). DIFileMacro will contain: * line number (interger). * file (DIFile). * macro list (MacroNodeArray) - optional. In addition, the DICom...

----- Original Message ----- > From: "Jakob Stoklund Olesen" <stoklund at 2pi.dk> > To: llvmdev at cs.uiuc.edu, llvmdev at cs.uiuc.edu, llvmdev at cs.uiuc.edu, llvmdev at cs.uiuc.edu > Sent: Thursday, March 21, 2013 1:26:25 PM > Subject: [LLVMdev] Simpler types in TableGen isel patterns > > Currently, instruction selection patterns are defined like this: >

...adata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIFileInclude" nodes. DIMacro will contain: • type (definition/undefinition). • line number (interger). • name (null terminated string). • replacement value (null terminated string - optional). DIFileMacro will contain: • line number (interger). • file (DIFile). • macro list (MacroNodeArray) - optional. I wonder if it'd b...

...adata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIFileInclude" nodes. DIMacro will contain: • type (definition/undefinition). • line number (interger). • name (null terminated string). • replacement value (null terminated string - optional). DIFileMacro will contain: • line number (interger). • file (DIFile). • macro list (MacroNodeArray) - optional. I wonder if it'd b...

...adata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIFileInclude" nodes. DIMacro will contain: • type (definition/undefinition). • line number (interger). • name (null terminated string). • replacement value (null terminated string - optional). DIFileMacro will contain: • line number (interger). • file (DIFile). • macro list (MacroNodeArray) - optional. I wonder if it'd b...

...; well: > > "DIMacro", "DIFileInclude", and "MacroNode". > > The last, is needed as we cannot use DINode as a base class of "DIMacro" > and DIFileInclude" nodes. > > > > DIMacro will contain: > > · type (definition/undefinition). > > · line number (interger). > > · name (null terminated string). > > · replacement value (null terminated string - optional). > > > > DIFileMacro will contain: > > · line number (interger). > > · file (DIFile). &gt...

...;, "DIFileInclude", and "MacroNode". >> >> The last, is needed as we cannot use DINode as a base class of "DIMacro" >> and DIFileInclude" nodes. >> >> >> >> DIMacro will contain: >> >> · type (definition/undefinition). >> >> · line number (interger). >> >> · name (null terminated string). >> >> · replacement value (null terminated string - optional). >> >> >> >> DIFileMacro will contain: >> >> · line number (...

...uot;MacroNode". >>> >>> The last, is needed as we cannot use DINode as a base class of "DIMacro" >>> and DIFileInclude" nodes. >>> >>> >>> >>> DIMacro will contain: >>> >>> · type (definition/undefinition). >>> >>> · line number (interger). >>> >>> · name (null terminated string). >>> >>> · replacement value (null terminated string - optional). >>> >>> >>> >>> DIFileMacro will contain:...

Currently, instruction selection patterns are defined like this: def : Pat<(and (not GR32:$src1), GR32:$src2), (ANDN32rr GR32:$src1, GR32:$src2)>; def : Pat<(and (not GR64:$src1), GR64:$src2), (ANDN64rr GR64:$src1, GR64:$src2)>; TableGen infers the types of $src1 and $src2 from the specified register classes, and that is the only purpose of the register