search for: annotate

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 e...

...r itself, parsing the llvm.global.annotations variable and adding annotations to the corresponding GlobalValues. This would 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 a...

I'm seeing a segfault on x86_64 Linux with the following code: desc = read.dcf("BAD") con = gzfile("test.gz", "wt") write.dcf(desc, file=con) close(con) where BAD has a long field (see below for example). The crash happens inside dummy_vfprintf. I think the issue is that the va_list ap is modified by the first vsnprintf call

Hello everyone, I am able to work very well with annotations in C/C++, by using __attribute__((annotate("MYANNOTATION"))) static int a; . Inside the LLVM bytecode I have @llvm.global.annotations and @llvm.var.annotation. However, I was trying to test annotations also in Java, with VMKit. These are the commands that I run: javac -Xlint -g -O Main.java ../Release+Asserts/bin/vmjc Main ../Re...

...ementation of annotations do not rely on LLVM > annotations. > > Regards, > > Harris Bakiras > > On 06/17/2013 02:19 PM, Alexandru Ionut Diaconescu wrote: > > Hello everyone, > > I am able to work very well with annotations in C/C++, by using > __attribute__((annotate("MYANNOTATION"))) static int a; . Inside the LLVM > bytecode I have @llvm.global.annotations and @llvm.var.annotation. > > However, I was trying to test annotations also in Java, with VMKit. These > are the commands that I run: > > javac -Xlint -g -O Main.java > ../R...

...produced. If I remember well, our implementation of annotations do not rely on LLVM annotations. Regards, Harris Bakiras On 06/17/2013 02:19 PM, Alexandru Ionut Diaconescu wrote: > Hello everyone, > > I am able to work very well with annotations in C/C++, by using > __attribute__((annotate("MYANNOTATION"))) static int a; . Inside the > LLVM bytecode I have @llvm.global.annotations and @llvm.var.annotation. > > However, I was trying to test annotations also in Java, with VMKit. > These are the commands that I run: > > javac -Xlint -g -O Main.java > ../...

...flexible enough. > We could also think about a user facing version of this while we are at it ;) > Do you mean providing a way for users to add their own annotation to say C/C++ code? The initial patch contains a Annotation2Metadata pass, which converts Clang annotations (` __attribute__((annotate("_name”))` ) to `!annotation` metadata. This allows users to use something like the snippet below, to annotate all instructions in a function by piggybacking on Clang’s annotate attribute. void __attribute__((annotate("__overflow_rt_check"))) custom_overflow_check(int a, int b) { …...

...es" function (x, ...) standardGeneric("annotation") <environment: 0x1a302b0> Methods may be defined for arguments: x Use showMethods("annotation") for currently available ones. > showMethods("annotation") Function: annotation (package IRanges) x="AnnotatedList" > Biobase:::annotation standardGeneric for "annotation" defined from package "Biobase" function (object) standardGeneric("annotation") <environment: 0x205cee0> Methods may be defined for arguments: object Use showMethods("annotation")...

...ly > on LLVM annotations. > > Regards, > > Harris Bakiras > > On 06/17/2013 02:19 PM, Alexandru Ionut Diaconescu wrote: >> Hello everyone, >> >> I am able to work very well with annotations in C/C++, by using >> __attribute__((annotate("MYANNOTATION"))) static int a; . Inside >> the LLVM bytecode I have @llvm.global.annotations and >> @llvm.var.annotation. >> >> However, I was trying to test annotations also in Java, with >> VMKit. These are the commands that I run: >>...

...It does not seem to be defined in > the LLVM > language reference, shouldn't it be? It's name suggests that it is a > reserved > variable name with a fixed type (similar to intrinsic functions?). Yes, we should document it. It is a convention established by the __builtin_annotate function in the c compilers. We should standardize it and document it. > Furthermore, it seems that the AnnotationManager that is currently > implemented > is capable of keeping a list of Annotations for any Annotatable > (currently > only Function). These annotations are kep...

...ions > variable and > adding annotations to the corresponding GlobalValues. This would > 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 m...

hi Chris! thanks for your reply. First of all I did not know about the history with the Annotation stuff. Annotable for me was a way how one could realize this things. So as I see it right now - it is more that Annotable will completly vanish soon. This is interesting to me. Chris Lattner schrieb: > On Fri, 24 Feb 2006, Jakob Praher wrote: > >> When translating a complex c

The following is a brief proposal for annotated assembly (and disassembly) output. Kevin Enderby and I have been discussing this a bit and are interested in getting broader feedback from interested folks. LLVM Rich Assembly Output LLVM's (dis)assembly output is currently very raw. Consumers have limited ability to introspect the instr...

...the thread local data section (.tdata), this would be interesting to have in llvm. like in GCC you write: int x __attribute__((section(".tdata"))); however the llvm bytecode (llvm-gcc -S) does not show anything like this attribute. There is this Annotable base class, which is used to annotate a MachineFunction to a LLVM Function. Function support Annotable but GlobalVariable as of 1.5 not. I would generally be interested and could contribute to extending LLVM by allowing more Annotatinons than currently possible. Why not make things like Instructions Annotable too? For instance pointe...

...tecode (llvm-gcc -S) does not show anything like this > attribute. LLVM 1.6 and the "new front-end" already handle this right. Here's the bugzilla bug corresponding to it: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=659 > There is this Annotable base class, which is used to annotate a > MachineFunction to a LLVM Function. Function support Annotable but > GlobalVariable as of 1.5 not. > > I would generally be interested and could contribute to extending LLVM > by allowing more Annotatinons than currently possible. > > Why not make things like Instructions A...

On Fri, 22 Sep 2023 10:32:05 -0700, Kees Cook wrote: > This is a batch of patches touching drm for preparing for the coming > implementation by GCC and Clang of the __counted_by attribute. Flexible > array members annotated with __counted_by can have their accesses > bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array > indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). > > As found with Coccinelle[1], add __counted_by to structs that would > benefit from the...

On Fri, 22 Sep 2023 10:32:05 -0700, Kees Cook wrote: > This is a batch of patches touching drm for preparing for the coming > implementation by GCC and Clang of the __counted_by attribute. Flexible > array members annotated with __counted_by can have their accesses > bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array > indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). > > As found with Coccinelle[1], add __counted_by to structs that would > benefit from the...

...so think about a user facing version of this while we are at it ;) >>> >> Do you mean providing a way for users to add their own annotation to say C/C++ code? >> >> The initial patch contains a Annotation2Metadata pass, which converts Clang annotations (` __attribute__((annotate("_name”))` ) to `!annotation` metadata. This allows users to use something like the snippet below, to annotate all instructions in a function by piggybacking on Clang’s annotate attribute. >> >> void __attribute__((annotate("__overflow_rt_check"))) custom_overflow_check...

On Fri, 22 Sep 2023 10:32:05 -0700, Kees Cook wrote: > This is a batch of patches touching drm for preparing for the coming > implementation by GCC and Clang of the __counted_by attribute. Flexible > array members annotated with __counted_by can have their accesses > bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array > indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). > > As found with Coccinelle[1], add __counted_by to structs that would > benefit from the...

...things like @llvm.var.annotation in dumps but no relevant sounding methods to get at these. Thank you On Thu, Sep 22, 2011 at 1:20 PM, Julien Lerouge <jlerouge at apple.com> wrote: > On Thu, Sep 22, 2011 at 02:46:05AM -0400, Mark Brown wrote: > > With recent work a plugin can now Annotate a VarDecl at the AST level, > how > > can this be used in a Pass at the IR level? What classes are responsible > for > > their manipulation? I assumed it would be part of Value, or something > common > > like it, but I do not see any mentions of Annotation or Attribute. &...