search for: annotation2metadata

...s cases during the bring-up would be very helpful to make sure the system is 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("__...

...ls, (2) shared variables, ..., are generated and how many survive. > >> 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...

...this should fit in nicely (hopefully) :) >> >>> 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__(...

Hi, I would like to propose a new !annotation metadata kind that can be attached to arbitrary instructions to drive generating remarks that provide additional insight into transformations applied to a program. To motivate this, consider these specific questions we would like to get answered: * How many stores added for automatic variable initialization remain after optimizations? Where are