search for: int_memorymarkers

...lls away > > where possible, replacing them with simple moves - at least as long as > > the number of bytes to copy does not exceed a certain threshold. > > > > As for the llvm.lifetime intrinsics, take a look at the documentation: > > http://llvm.org/docs/LangRef.html#int_memorymarkers > > If I'm not mistaken, these calls seem to be used to mark the lifespan of > > a stack-allocated object. > > > > Regards, > > Christoph > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at...

...rmally optimizes these calls away > where possible, replacing them with simple moves - at least as long as > the number of bytes to copy does not exceed a certain threshold. > > As for the llvm.lifetime intrinsics, take a look at the documentation: > http://llvm.org/docs/LangRef.html#int_memorymarkers > If I'm not mistaken, these calls seem to be used to mark the lifespan of > a stack-allocated object. > > Regards, > Christoph > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120305/b...

Clang is inserting an llvm.memcpy function call into my program where it does not exist (the code never calls memcpy), is there a particular reason for this? It also looks like it's inserting two other artificial function calls, something to do with llvm.lifetime.start and llvm.lifetime.end, what are these functions and why are they being inserted artificially? Thanks. -------------- next

...lls away > > where possible, replacing them with simple moves - at least as long as > > the number of bytes to copy does not exceed a certain threshold. > > > > As for the llvm.lifetime intrinsics, take a look at the documentation: > > http://llvm.org/docs/LangRef.html#int_memorymarkers > > If I'm not mistaken, these calls seem to be used to mark the lifespan of > > a stack-allocated object. > > > > Regards, > > Christoph > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at...

...s is that the backend normally optimizes these calls away where possible, replacing them with simple moves - at least as long as the number of bytes to copy does not exceed a certain threshold. As for the llvm.lifetime intrinsics, take a look at the documentation: http://llvm.org/docs/LangRef.html#int_memorymarkers If I'm not mistaken, these calls seem to be used to mark the lifespan of a stack-allocated object. Regards, Christoph

...mally optimizes these calls away > where possible, replacing them with simple moves - at least as long as > the number of bytes to copy does not exceed a certain threshold. > > As for the llvm.lifetime intrinsics, take a look at the documentation: > http://llvm.org/docs/LangRef.html#int_memorymarkers > If I'm not mistaken, these calls seem to be used to mark the lifespan of > a stack-allocated object. > > Regards, > Christoph > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.ed...

...;> where possible, replacing them with simple moves - at least as long as >>> the number of bytes to copy does not exceed a certain threshold. >>> >>> As for the llvm.lifetime intrinsics, take a look at the documentation: >>> http://llvm.org/docs/LangRef.html#int_memorymarkers >>> If I'm not mistaken, these calls seem to be used to mark the lifespan of >>> a stack-allocated object. >>> >>> Regards, >>> Christoph >>> >>> _______________________________________________ >>> LLVM Developers mailing...

...e, replacing them with simple moves - at least as long as > >>> the number of bytes to copy does not exceed a certain threshold. > >>> > >>> As for the llvm.lifetime intrinsics, take a look at the documentation: > >>> http://llvm.org/docs/LangRef.html#int_memorymarkers > >>> If I'm not mistaken, these calls seem to be used to mark the lifespan > of > >>> a stack-allocated object. > >>> > >>> Regards, > >>> Christoph > >>> > >>> ______________________________________________...

Ahh, this states the problem precisely. Does anyone know if there is active development in this direction? I'd love to be able to use llvm.lifetime.start() / end(). Scott On Fri, Dec 11, 2009 at 12:12 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello, Scott > >> I've just started using LLVM for a project I'm working on, and the >> docs seem

...here possible, replacing them with simple moves - at least as long as > > > the number of bytes to copy does not exceed a certain threshold. > > > > > > As for the llvm.lifetime intrinsics, take a look at the documentation: > > > http://llvm.org/docs/LangRef.html#int_memorymarkers > > > If I'm not mistaken, these calls seem to be used to mark the lifespan > of > > > a stack-allocated object. > > > > > > Regards, > > > Christoph > > > > > > _______________________________________________ > > > LLVM...

...m with simple moves - at least as long as >> >>> the number of bytes to copy does not exceed a certain threshold. >> >>> >> >>> As for the llvm.lifetime intrinsics, take a look at the documentation: >> >>> http://llvm.org/docs/LangRef.html#int_memorymarkers >> >>> If I'm not mistaken, these calls seem to be used to mark the lifespan >> of >> >>> a stack-allocated object. >> >>> >> >>> Regards, >> >>> Christoph >> >>> >> >>> ______________...