search for: undefinitely

Displaying 13 results from an estimated 13 matches for "undefinitely".

Did you mean: indefinitely
2012 Mar 03
2
keywords/flags questions
...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 -
2005 Sep 24
1
booting from copied ext3 software raid fs to normal fs
.... 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-11...
2002 Mar 26
0
Problem running Win32 app under Wine
Hi to every one, I am using MandrakeLinux 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.
2011 May 24
0
Xen and live migration with VIR_MIGRATE_PERSIST_DEST
Hi, I'm having a hard time to figure how to perform Xen live migration using the 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
2015 Oct 28
4
RFC: Supporting macros in LLVM debug info
Hi, I would like to implement macro debug info support in LLVM. Below you will find 4 parts: 1. Background on what does it mean to debug macros. 2. A brief explanation on how to represent macro debug info in DWARF 4.0. 3. The suggested design. 4. A full example: Source -> AST -> LLVM IR -> DWARF. Feel free to skip first two parts if you think you know the background.
2013 Mar 21
0
[LLVMdev] Simpler types in TableGen isel patterns
----- 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: >
2015 Nov 03
3
RFC: Supporting macros in LLVM debug info
> Do we really need to touch the AST? Or would it be reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) This sound as a good idea, I will check that approach. PPCallbacks is only an interface, has nothing connected to it, but we will create a new class, which implement PPCallbacks, for macros. So we can
2015 Nov 03
2
RFC: Supporting macros in LLVM debug info
> Not necessarily, if we kept the macros in order in the list of macros attached to the CU, which I imagine we would. OK, now I understand what you are aiming for. I really do not favor one on the other. But, can you explain what is the advantage of the parent approach over the children approach? If any, the children approach seems to be the one reduces the LLVM IR size, is not it? Regards,
2015 Nov 05
2
RFC: Supporting macros in LLVM debug info
> Right - I was wondering if CGDebugInfo already implemented PPCallbacks or was otherwise being notified of PPCallback related things, possibly through a layer or two of indirection. I checked the approach of skipping representing macros in AST, and communicate them directly from Parser to CGDebugInfo. However, I could not find a way to initialize this communication. The only interface
2015 Nov 13
2
RFC: Supporting macros in LLVM debug info
On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> wrote: > I found a way to skip representing macros in AST and create them directly > in CGDebugInfo through PPCallbacks during preprocessing. > > To do that, I needed to extend ASTConsumer interface with this extra > method: > > > > /// If the consumer is interested in notifications from
2015 Nov 04
2
RFC: Supporting macros in LLVM debug info
I'd like to jump in. I do not work on a preprocessor based language, but have the same code expansion problem to encode. Right now, we hack around the problem by appending some prefix after the file name and pretend it is a different file, which is not great. I understand you want to represent expansion by DIFileMacro ? I'm not how this is supposed to be used and it is not in the example.
2015 Nov 13
2
[cfe-dev] RFC: Supporting macros in LLVM debug info
On Fri, Nov 13, 2015 at 2:41 PM, Richard Smith <richard at metafoo.co.uk> wrote: > On Fri, Nov 13, 2015 at 10:21 AM, David Blaikie via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> >> wrote: >> >>> I found a way to skip representing macros in AST and create them
2013 Mar 21
9
[LLVMdev] Simpler types in TableGen isel patterns
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