search for: mark_m

...c++ source) and after emit some special > "information" for them at codegen stage (so, actually, I'm wanting to > find "marked" functions at some pass, etc). > > I can introduce special attribute to allow user mark function as > void foo() __attribute__(("mark_me")); > and than do lookup_attribute() call inside llvv-gcc backend. > > Is there any "standard" way to introduce some flags for Functions/GVs > inside LLVM? Or I should introduce some new "structure", change bytecode > format, etc. > > It seems to me, t...

...-compat: prevent options overwrite ebtables-compat: prevent same matches to be included multiple times ebtables-compat: include rule counters in ebtables rules ebtables-compat: fix nft payload bases ebtables-compat: add 'ip' match extension ebtables-compat: add mark_m match extension extensions: cleanup commented code in ebtables-compat extensions libxtables: search first for AF-specific extension ebtables-compat: call extensions final checks ebtables-compat: finish target infrastructure ebtables-compat: add mark target extension...