Displaying 4 results from an estimated 4 matches for "globalannot".
2008 Jun 25
0
[LLVMdev] Using annotation attributes
...d just leave the
annotations in the IR as well, so that transformation passes would properly
preserve them (and, just like debug info, sometimes be prevented from
modifying some annotated global values unless they are taught how to preserve
the annotations).
By using a subclass of Annotation (say, GlobalAnnotation) we can distinguish
between annotations that are (or should be) in the IR and (the existing)
annotations that should be in memory only. This would also allow for newly
added annotations to be immediately be added to the IR, ensuring that the
AnnotationManager's view remains consistent with...
2008 Jun 05
5
[LLVMdev] Using annotation attributes
Hi,
I'm trying to annotate certain functions in C code, and do something with
these functions in my LLVM pass. I annotate the C code like this:
int __attribute__((annotate("annot"))) function() {
This nicely gets added to the LLVM bitcode in an
@llvm.global.annotations global. Now I had hoped that it'd be easy to extract
a list of functions annotated with my annotation
2008 Jun 28
1
[LLVMdev] Using annotation attributes
...lobal values unless they are taught how to
> preserve
> the annotations).
Makes sense. This is similar to how the MachineDebugInfo stuff
deserializes debug info out of the LLVM IR and presents it for easy
consumption of the code generator.
> By using a subclass of Annotation (say, GlobalAnnotation) we can
> distinguish
> between annotations that are (or should be) in the IR and (the
> existing)
> annotations that should be in memory only. This would also allow for
> newly
> added annotations to be immediately be added to the IR, ensuring
> that the
> Anno...
2008 Sep 13
1
[LLVMdev] Using annotation attributes
...as well, so that transformation passes would
> properly
> preserve them (and, just like debug info, sometimes be prevented from
> modifying some annotated global values unless they are taught how to
> preserve
> the annotations).
>
> By using a subclass of Annotation (say, GlobalAnnotation) we can
> distinguish
> between annotations that are (or should be) in the IR and (the
> existing)
> annotations that should be in memory only. This would also allow for
> newly
> added annotations to be immediately be added to the IR, ensuring
> that the
> Anno...