similar to: [LLVMdev] attribute/annotation surviving for pass?

Hi Mark, I don't know anything about Clang's annotations or attributes, but from what you describe it sounds like you want to attach metadata to Values? Try searching for "metadata" instead, that should get you more results :) Cheers, James From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Mark Brown Sent: 22 September 2011 07:46 To:

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. > > Thank you

How can they processed? I cant seem to find any solid information about how they exist in IR form from a Passes perspective. I see 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

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. Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL:

> 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

Hi Asit, thanks for the reply. But I guess I was not clear in my question. Actually, i dont want to use __ATTRIBUTE__((ANNOTATE("MOVIATTR"))), since in documentation it is stated that "This intrinsic allows annotation of local variables with arbitrary strings. This can be useful for special purpose optimizations that want to look for these annotations. These have no other

On Jun 25, 2008, at 6:33 AM, Matthijs Kooijman wrote: > Hi all, Howdy Matthijs, > I've also been developing an interest in using IR annotations for my > compiler. > Some discussion with Bart turns out that he has implemented some > code to parse > the llvm.globals.annotations array, but in no way integrated or > reusable. > We've spent some thought about how

Hi John, I have looked into the EmitAutoVarAlloca() in CGDecl.cpp. However, I could not figure out how to employ my custom attribute for code generation. For example, my custom attribute is visible in CGDecl.cpp but how can I generate based on my custom attribute if (D.hasAttr<myCustomAttri>()) { //What to do here? } What I wan in IR is something like below. Without Custom Attribute:

Hi Florian, On 11/9/20 5:09 AM, Florian Hahn wrote: > >> On Nov 6, 2020, at 17:32, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: >> >> Cool! I really like the idea. I left a comment about metadata preservation below. >> Once this is available we will certainly employ it to understand OpenMP programs better. > That sounds like a great use case!

Hi all I have a project where LLVM annotations could be very useful. My current understanding of LLVM in general is still limited, hence a nice interface to annotations or sample code that uses annotations would help me to get started. I was wondering what happened to the proposal for a better interface to handling of annotations, which has been discussed in this thread back in July.

> On Nov 9, 2020, at 19:27, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > On 11/9/20 5:09 AM, Florian Hahn wrote: >> >>> On Nov 6, 2020, at 17:32, Johannes Doerfert <johannesdoerfert at gmail.com <mailto:johannesdoerfert at gmail.com>> wrote: >>> >>> Cool! I really like the idea. I left a comment about metadata preservation

Many of you on the llvm-dev list have requested this, so I've added a new attribute to llvm-gcc. The "annotate" attribute can be used to annotate functions, global and local variables with arbitrary strings. This can be useful for special purpose optimizations and are ignored by code generation. For functions and global variables, the annotations are represented in a global

Hi Tanya, In the long term, how are different uses of this string going to be kept from conflicting? Is this going to introduce another mini-syntax into LLVM, to allow different passes to recognize which pass the string is intended for, or to allow passes to pull out selected substrings and ignore the rest? Dan On Mon, Jun 18, 2007 at 04:44:54PM -0700, Tanya M. Lattner wrote: > > Many of

Hi all, I've also been developing an interest in using IR annotations for my compiler. Some discussion with Bart turns out that he has implemented some code to parse the llvm.globals.annotations array, but in no way integrated or reusable. We've spent some thought about how this could be done properly, which I will share here. Firstly, however, I was wondering about the format of the

Hi All, I need your guidance about a custom attribute. I have defined one for variables. It is accepted in the source code (without any warnings from clang), for example in following snippet. #define NEWATTR __attribute__((moviAttr(1))) int main() { NEWATTR volatile unsigned int a = 5; volatile unsigned int *p; p = &a; return (a+*p); } and actually when I Dump the declaration, after

Cool! I really like the idea. I left a comment about metadata preservation below. Once this is available we will certainly employ it to understand OpenMP programs better. We could also think about a user facing version of this while we are at it ;) ~ Johannes On 11/4/20 3:57 PM, Florian Hahn via llvm-dev wrote: > Hi, > > > I would like to propose a new !annotation metadata kind

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

> On Nov 6, 2020, at 17:32, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > > Cool! I really like the idea. I left a comment about metadata preservation below. > Once this is available we will certainly employ it to understand OpenMP programs better. That sounds like a great use case! Having multiple different uses cases during the bring-up would be very helpful to

> I created a plugin to add simple Annotations to VarDecls and > FieldDecls, and write this modified AST out to a file. I notice that > when I use clang to compile this file I get different code then when I > use the source directly. In both cases I'm compiling with -O4. Can > anyone explain this? This is how clang implements annotations on local variables, that's all.

Hi Timothy, Appreciate the comprehensive code review. The biggest issue I see is the peak stack usage.... rest looks like fairly straight forward cleanup. Is the peak stack usage a complete blocker in current form? If it is indeed a blocker, would it be acceptable if we can reduce additional buffer requirement from 2 buffers (current) to 1, possibly by moving scaling inside