[PATCH] news: Describe AArch64-specific changes

[Wilco Dijkstra]

Hi Yury,


> +* On AArch64 targets that support Guarded Control Stack extension all GCS
> +  operations (including status, write on shadow stack, and push to shadow
> +  stack) are locked when GCS is enabled unless OPTIONAL GCS policy is used.

What does "are locked" mean? Does it mean enabled/checked or the instructions trap?

> +* On AArch64 targets, malloc-family functions are implemented as GNU indirect
> +  functions (ifuncs).

Is this news? It's not user visible, neither does it do anything new or different...

> +* The configure script will no longer use the --enable-memory-tagging flag.
> +  The corresponding AArch64-specific functionality that was previously
> +  activated by this flag was removed as well.

Maybe "The --enable-memory-tagging configure option has been removed."?

Cheers,
Wilco