On Mon, 9 Dec 2024, Jakub Jelinek wrote:
> Hi!
>
> Since GCC 13 -fsanitize=hwaddress is not supported just on AArch64, but also
> on x86_64 (but only with -mlam=u48 or -mlam=u57).
>
> Ok for trunk?
OK.
> 2024-12-09 Jakub Jelinek <ja...@redhat.com>
>
> PR sanitize/117960
> * doc/invoke.texi (fsanitize=hwaddress): Clarify on which targets
> it is supported.
>
> --- gcc/doc/invoke.texi.jj 2024-12-09 11:37:50.282218643 +0100
> +++ gcc/doc/invoke.texi 2024-12-09 13:45:32.431473662 +0100
> @@ -17768,8 +17768,10 @@ the available options are shown at start
>
> @url{https://github.com/google/sanitizers/wiki/AddressSanitizerFlags#run-time-flags}
> for a list of supported options.
> The option cannot be combined with @option{-fsanitize=thread} or
> -@option{-fsanitize=hwaddress}. Note that the only target
> -@option{-fsanitize=hwaddress} is currently supported on is AArch64.
> +@option{-fsanitize=hwaddress}. Note that the only targets
> +@option{-fsanitize=hwaddress} is currently supported on are x86-64
> +(only with @code{-mlam=u48} or @code{-mlam=u57} options) and AArch64,
> +in both cases only in ABIs with 64-bit pointers.
>
> To get more accurate stack traces, it is possible to use options such as
> @option{-O0}, @option{-O1}, or @option{-Og} (which, for instance, prevent
>
> Jakub
>
>
--
Richard Biener <rguent...@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
