Displaying 6 results from an estimated 6 matches for "llvmreplacealluseswith".
2016 Feb 24
3
How to resolve debug info forward types
Before metadata was separated from values, I could create a debug info forward
declaration and eventually resolve it using LLVMReplaceAllUsesWith in core.h.
Now, I can't figure out how to resolve it. I can find no function that seems
to do this. My one wild guess that giving the forward decl and the resolving
decl the same UniqueId might do it is not working.
I am currently using 3.6.1, but I see nothing the voluminous diff of DIBuild...
2016 Feb 24
0
How to resolve debug info forward types
...outstanding temporary forward declarations
to do this.
On Wed, Feb 24, 2016 at 5:09 PM, Rodney M. Bates via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Before metadata was separated from values, I could create a debug info
> forward
> declaration and eventually resolve it using LLVMReplaceAllUsesWith in
> core.h.
> Now, I can't figure out how to resolve it. I can find no function that
> seems
> to do this. My one wild guess that giving the forward decl and the
> resolving
> decl the same UniqueId might do it is not working.
>
> I am currently using 3.6.1, but I see...
2009 Oct 08
2
[LLVMdev] Some additions to the C bindings
...Kenneth!
I wouldn't say that I'm the best reviewer, but I've been doing some
work with the c bindings recently so hopefully I have some idea of
what I'm talking about :) Comments are inlined:
+/** See the llvm::Use class. */
+typedef struct LLVMOpaqueUse *LLVMUseRef;
+
...
+void LLVMReplaceAllUsesWith(LLVMValueRef OldVal, LLVMValueRef NewVal);
...
+/* Operations on Uses */
+LLVMUseRef LLVMGetFirstUse(LLVMValueRef Val);
+LLVMUseRef LLVMGetNextUse(LLVMUseRef U);
+LLVMValueRef LLVMGetUser(LLVMUseRef U);
+LLVMValueRef LLVMGetUsedValue(LLVMUseRef U);
These seem okay to me, but I don't have too...
2009 Oct 07
0
[LLVMdev] Some additions to the C bindings
On Tue, Oct 6, 2009 at 2:13 PM, Kenneth Uildriks <kennethuil at gmail.com> wrote:
> My front-end is sync'd with the trunk now, and working well, but it
> required some additional functions exposed in the C bindings. I
> hereby submit them for review and approval for inclusion in the trunk.
>
LLVMGetAttribute had a bug in it. Here's the revised version of the patch
2009 Oct 06
3
[LLVMdev] Some additions to the C bindings
My front-end is sync'd with the trunk now, and working well, but it
required some additional functions exposed in the C bindings. I
hereby submit them for review and approval for inclusion in the trunk.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cbindings.patch
Type: application/octet-stream
Size: 7269 bytes
Desc: not available
URL:
2009 Oct 08
0
[LLVMdev] Some additions to the C bindings
...code, since it's the generated code that
creates all of the "regular" functions. Generated code has a much
easier time calling the C bindings than the C++ API.
>
>
> +/** See the llvm::Use class. */
> +typedef struct LLVMOpaqueUse *LLVMUseRef;
> +
> ...
> +void LLVMReplaceAllUsesWith(LLVMValueRef OldVal, LLVMValueRef NewVal);
> ...
> +/* Operations on Uses */
> +LLVMUseRef LLVMGetFirstUse(LLVMValueRef Val);
> +LLVMUseRef LLVMGetNextUse(LLVMUseRef U);
> +LLVMValueRef LLVMGetUser(LLVMUseRef U);
> +LLVMValueRef LLVMGetUsedValue(LLVMUseRef U);
>
>
> These...