https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80053
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The manual does say:
You may not use this mechanism to jump to code in a different function. If you
do that, totally unpredictable things happen. The best way to avoid this is to
store the label address only in automatic variables and never pass it as an
argument.
And even says (which was added back in r0-94877 which was in 2009):
The &&foo expressions for the same label might have different values if the
containing function is inlined or cloned. If a program relies on them being
always the same, __attribute__((__noinline__,__noclone__)) should be used to
prevent inlining and cloning. If &&foo is used in a static variable
initializer, inlining and cloning is forbidden.
So I think we can say we document the label as values extension in a decent
way. Just you want to abuse it more.
