From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 2862A385841C; Sat, 30 Mar 2024 03:55:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2862A385841C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1711770925;
	bh=PI/uVGZc9DKnbV/ihlYIM5LkAyDGYrPSSImGoo5Utd0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Q1QlRCm1ddhNDbuxmoGRd1HzjxrD3bfQQEDkUvpfDqForlK8s5PYNYUVEX0GpTudi
	 VEUu2YFYKZouf8K/YRtK2uCv8YvEkVSxQ4oQRjihgJf6HQtXX890OH26+FPI9iXoJ9
	 zi949HEguB3V1l5Q9/z28mKyIfeNjM3mjy3zriUE=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/111736] Address sanitizer is not compatible with
 named address spaces
Date: Sat, 30 Mar 2024 03:55:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 12.1.0
X-Bugzilla-Keywords: addr-space, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111736-4-MLKngxvr4G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111736

--- Comment #31 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:05de873353ab9e94cda2b9e9561a82ca4e061c3f

commit r13-8520-g05de873353ab9e94cda2b9e9561a82ca4e061c3f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 22 09:23:44 2024 +0100

    ubsan: Don't -fsanitize=3Dnull instrument __seg_fs/gs pointers [PR11173=
6]

    On x86 and avr some address spaces allow 0 pointers (on avr actually
    even generic as, but libsanitizer isn't ported to it and
    I'm not convinced we should completely kill -fsanitize=3Dnull in that
    case).
    The following patch makes sure those aren't diagnosed for -fsanitize=3D=
null,
    though they are still sanitized for -fsanitize=3Dalignment.

    2024-03-22  Jakub Jelinek  <jakub@redhat.com>

            PR sanitizer/111736
            * ubsan.cc (ubsan_expand_null_ifn, instrument_mem_ref): Avoid
            SANITIZE_NULL instrumentation for non-generic address spaces
            for which targetm.addr_space.zero_address_valid (as) is true.

            * gcc.dg/ubsan/pr111736.c: New test.

    (cherry picked from commit ddd4a3ca87410886b039cc225907b4f6e650082e)=