https://gcc.gnu.org/g:2e958291ff68d9bff1092895a14b6763de56823b

commit r15-6040-g2e958291ff68d9bff1092895a14b6763de56823b
Author: Jakub Jelinek <ja...@redhat.com>
Date:   Mon Dec 9 14:17:39 2024 +0100

    docs: Clarify -fsanitize=hwaddress target support [PR117960]
    
    Since GCC 13 -fsanitize=hwaddress is not supported just on AArch64, but also
    on x86_64 (but only with -mlam=u48 or -mlam=u57).
    
    2024-12-09  Jakub Jelinek  <ja...@redhat.com>
    
            PR sanitizer/117960
            * doc/invoke.texi (fsanitize=hwaddress): Clarify on which targets
            it is supported.

Diff:
---
 gcc/doc/invoke.texi | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index daab28908684..14afd1934bd2 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -17768,8 +17768,10 @@ the available options are shown at startup of the 
instrumented program.  See
 
@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

Reply via email to