https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122483
--- Comment #24 from Alex Coplan <acoplan at gcc dot gnu.org> ---
I meant the tree-core.h:attribute_spec flags, which currently has:
/* Whether this attribute requires a DECL. If it does, it will be passed
from types of DECLs, function return types and array element types to
the DECLs, function types and array types respectively; but when
applied to a type in any other circumstances, it will be ignored with
a warning. (If greater control is desired for a given attribute,
this should be false, and the flags argument to the handler may be
used to gain greater control in that case.) */
bool decl_required;
/* Whether this attribute requires a type. If it does, it will be passed
from a DECL to the type of that DECL. */
bool type_required;
/* Whether this attribute requires a function (or method) type. If it does,
it will be passed from a function pointer type to the target type,
and from a function return type (which is not itself a function
pointer type) to the function type. */
bool function_type_required;
/* Specifies if attribute affects type's identity. */
bool affects_type_identity;
those flags are under the control of the aarch64 backend for aarch64-specific
attributes, we currently have:
static const attribute_spec aarch64_arm_attributes[] =
{
{ "streaming", 0, 0, false, true, true, true,
NULL, attr_streaming_exclusions },
...
}
in aarch64.cc.
