search for: __overflow_rt_check

...ta 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) { … } >> >> >> The proposal boils down to three parts. >> >> The first part consists of adding a new metadata kind (!annotation ) to allow tagging of ‘interesting’ instructions. For example, Clang could add this metadat...

...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) { … } This is pretty much what I had in mind :). I didn't go over the initial patch so I missed it. > >>> >>> The proposal boils down to three parts. >>> >>> The first part consists of adding a new metadata...

...verts 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) { … } > > This is pretty much what I had in mind :). I didn't go over the initial patch so I missed it. > It seems to work quite well in practice, with the caveat that it is not possible to mark blocks/statements individually. But it shou...

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