Displaying 3 results from an estimated 3 matches for "subinstructions".
Did you mean:
siinstructions
2008 Jul 11
0
[LLVMdev] Cloning Functions
...all the pristine Function clones, they are now cloned into the
cloned Module.
This should work as I understand things, but I have a question about
Function::deleteBody. It calls dropAllReferences which has the following
scary comment:
/// dropAllReferences() - This method causes all the subinstructions to "let
/// go" of all references that they are maintaining. This allows one to
/// 'delete' a whole module at a time, even though there may be circular
/// references... first all references are dropped, and all use counts go to
/// zero. Then everything is deleted for...
2008 Jul 09
2
[LLVMdev] Cloning Functions
On Wednesday 09 July 2008 13:24, Devang Patel wrote:
> Is it possible to explain intended use of original unoptimized version ?
bugpoint. I want to run it on the IR produced by our frontend. This will
help us generate new LLVM tests we can send upstream. We've fixed
bugs that aren't caught by the upstream tests and it would be nice to capture
the problem and make the test
2008 Jul 11
2
[LLVMdev] Cloning Functions
...loned into
> the
> cloned Module.
>
> This should work as I understand things, but I have a question about
> Function::deleteBody. It calls dropAllReferences which has the
> following
> scary comment:
>
> /// dropAllReferences() - This method causes all the
> subinstructions to "let
> /// go" of all references that they are maintaining. This allows
> one to
> /// 'delete' a whole module at a time, even though there may be
> circular
> /// references... first all references are dropped, and all use
> counts go to
> /// z...