search for: reuse

On Thu, Jun 26, 2014 at 3:39 PM, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > The main motivation for turning it off is that no known consumer (debugger) > took advantage of it. > > Turning it on does more than slightly increase the object file size, it can > cause the same source line to be listed multiple times in the .debug_line > table (with different

The UDP binding logic will reuse local port numbers immediately. This causes problems for TFTP, which assumes a very low probability of a source port number being reused. The consequence is that lpxelinux.0 may end up downloading an incorrect file (e.g. attempting to download pxelinux.cfg/default but actually receiving a copy of...

...by how much (but I think by a > > significant amount). > > Do you mean it will re-use memory less often? Won't that just hide > the bug above? If anything, I don't want ASan to "mitigate" bugs, I > want it to make the bug trigger more often. :) > ASan's reuses it less often, but keeps it poisoned so that dangling pointers get caught. This makes it less likely that re-use will cause invalid analysis results. BUT it makes it more likely that when we access a dangling pointer, it falls into a poisoned heap area. So the net result is that it catches danglin...

...Yes I know that the patch by Davidlohr Bueso has a typo in the subject :( Davidlohr Bueso (1): lcoking/barriers, arch: Use smp barriers in smp_store_release() Michael S. Tsirkin (40): asm-generic: guard smp_store_release/load_acquire ia64: rename nop->iosapic_nop ia64: reuse asm-generic/barrier.h powerpc: reuse asm-generic/barrier.h s390: reuse asm-generic/barrier.h sparc: reuse asm-generic/barrier.h arm: reuse asm-generic/barrier.h arm64: reuse asm-generic/barrier.h metag: reuse asm-generic/barrier.h mips: reuse asm-generic/ba...

...Yes I know that the patch by Davidlohr Bueso has a typo in the subject :( Davidlohr Bueso (1): lcoking/barriers, arch: Use smp barriers in smp_store_release() Michael S. Tsirkin (40): asm-generic: guard smp_store_release/load_acquire ia64: rename nop->iosapic_nop ia64: reuse asm-generic/barrier.h powerpc: reuse asm-generic/barrier.h s390: reuse asm-generic/barrier.h sparc: reuse asm-generic/barrier.h arm: reuse asm-generic/barrier.h arm64: reuse asm-generic/barrier.h metag: reuse asm-generic/barrier.h mips: reuse asm-generic/ba...

I'm looking for a way to approximate the "zero-overhead" model of code reuse available in languages like Python, Perl, etc. I've described this idea in more detail, and the motivation for this question in an earlier post to R-help (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html). (One of the responses I got advised that I post my question here instea...

Dear LLVM-Mailing-List, I'm using the llvm::EngineBuilder to create an instance of the llvm::ExecutionEngine, I then JIT my code, take the addresses I need and delete the llvm::ExecutionEngine. But now I started to wonder, if I could reuse that instance for a new module again? I first tried calling llvm::EngineBuilder without setting a Module, I planned to add it later - but when I do this the "create" function will crash. Another test I ran was calling "removeModule" of the llvm::ExecutionEngine after the call...

Heyho, I can only provide you with a screenshot for the first problem I noticed: [https://media.discordapp.net/attachments/534012750045642783/575369402195640321/unknown.png] This code will crash when calling "eeBuilder.create". But I also looked at what happens if I do reuse the llvm::ExecutionEngine. After the call to "finalizeObject" I use "removeModule" for the Module I used. If I know parse the same module again and pass it to that llvm::ExecutionEngine, it will notice the duplication and rename the symbols, like when it does when you add the sa...

...%EFLAGS<imp-def,dead> ; srcLine 0 2816 %reg1591<def> = ADD64rr %reg1591, %reg1579, %EFLAGS<imp-def,dead> ; srcLine 0 2820 %reg1198<def> = LEA64r %reg1591, 1, %reg1574, 0 ; srcLine 0 ##### %reg1591 gets spilled by linear scan with all of the uses in the sequence above reused by the "spltting" code in LiveIntervals. Note especially that %reg1591 is (correctly) identified at rematable (for the SUB64rr): ##### spilling(a): %reg1591,3.3557 = [2178,2802:4)[2802,2810:3)[2810,2818:2) [2818,2966:1)[2966,7840:0) 0 at 2966 1 at 2818-(2966) 2 at 2810-(2818) 3 at...

https://bugzilla.samba.org/show_bug.cgi?id=6816 Summary: Delta-transfer algorithm does not reuse already transmitted identical blocks Product: rsync Version: 3.0.5 Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba....

...connection between different agi's.Actually when call comes to asterisk box it executes various agi scripts sequentially. Each script checks various values by making a new?MySQL?connection and then execute query and then disconnects.? So,?Ideally?there should be one connection, and it should be reused between each agi and when a call is over it should be disconnected. Is there any?mechanism?to reuse single?MySQL?connection?between agi scripts?The agi scripts are written in?Perl Thanks, Faheem, M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http:/...

Hi, Is it generally safe to cache a FunctionPassManager and reuse it on modules other than the one it was constructed with (assuming they have the same target triple)? paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110923/cd845b59/attachment.html>

...home/rich/llvm-trunk-new/lib/CodeGen/SelectionDAG/ScheduleDAG.cpp:141: void llvm::ScheduleDAG::BuildSchedUnits(): Assertion `N->getNodeId() == -1 && "Node already inserted!"' failed I'm guessing that's because I'm reusing Op1 and Op2. What is the right way to reuse DAG operands? -Rich

...las at mxc.ca] Sent: Saturday, September 24, 2011 12:21 PM To: Redmond, Paul Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] reusing FunctionPassManager with different Modules On 09/23/2011 11:28 AM, Redmond, Paul wrote: > Hi, > > Is it generally safe to cache a FunctionPassManager and reuse it on > modules other than the one it was constructed with (assuming they have > the same target triple)? No. FunctionPass has a pair of methods, doInitialization and doFinalization, which take Module& and are allowed to read or modify it outside runOnFunction. Nick

...017 06:29 AM, Nema, Ashutosh wrote: >>> Thanks for looking into this. >>> >>> 1) Issues with re running vectorizer: >>> Vectorizer might generate redundant alias checks while vectorizing epilog loop. >>> Redundant alias checks are expensive, we like to reuse the results of already computed alias checks. >>> With metadata we can limit the width of epilog loop, but not sure about reusing alias check result. >>> Any thoughts on rerunning vectorizer with reusing the alias check result ? >> >> One way of looking at this is: Re...

...tride-nine-with-base-reg.ll Failed with exit(1) at line 2 while running: llvm-as < test/CodeGen/X86/stride-nine-with-base-reg.ll | llc -march=x86-64 | not grep lea leaq B, %rdx leaq A, %r8 leaq P, %rdx child process exited abnormally FAIL: test/CodeGen/X86/stride-reuse.ll Failed with exit(1) at line 2 while running: llvm-as < test/CodeGen/X86/stride-reuse.ll | llc -march=x86-64 | not grep lea leaq B, %rsi leaq A, %rsi leaq P, %rsi child process exited abnormally

...ing redundancy ) as * store i32 %sub, i32* %k, align 4* and can delete the statement *%sub1 = sub nsw i32 %tmp2, %tmp3 * But, If in case LLVM is reusing *%sub *in between to hold some other computations, then there will be some errors in my computation. So I want to make sure that LLVM won't reuse any of these virtual registers. I hope it clarifies. On 18 March 2016 at 13:39, mats petersson <mats at planetcatfish.com> wrote: > > > On 18 March 2016 at 06:31, Ansar K.A. via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I meant LLVM registers. Thanks...

...ie wrote: > Details about this can be found here: > > https://lwn.net/Articles/750770/ > > What's new in this version > ========================== > > There are three choices based on the discussion [1] in RFC v2: > > > #1. We expose a VFIO device, so we can reuse the VFIO container/group > > based DMA API and potentially reuse a lot of VFIO code in QEMU. > > > > But in this case, we have two choices for the VFIO device interface > > (i.e. the interface on top of VFIO device fd): > > > > A) we may invent a...

...ie wrote: > Details about this can be found here: > > https://lwn.net/Articles/750770/ > > What's new in this version > ========================== > > There are three choices based on the discussion [1] in RFC v2: > > > #1. We expose a VFIO device, so we can reuse the VFIO container/group > > based DMA API and potentially reuse a lot of VFIO code in QEMU. > > > > But in this case, we have two choices for the VFIO device interface > > (i.e. the interface on top of VFIO device fd): > > > > A) we may invent a...

...n (Centos 5). There's an existing LVM with lots of partitions. Most are used for Xen guests. The system itself uses only one of them plus a separate /boot partition that is not on LVM. What's the best course of action here? Should I do the reinstall with kickstart or better manually and reuse the existing filesystem? As I understand once LVM gets loaded it should find the volumes by itself, but will it be able to use the same naming scheme for instance? Or do I have to do some additional stuff, anyway? Thanks, Kai