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 EEA65386C58E; Tue, 28 May 2024 17:09:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EEA65386C58E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1716916163;
	bh=ArWLaeLKiVvMVYH9lytkbREzTdkhiFOhqp+Cj/gLa+I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=m+FRdiItdqCXE+dole4ogvkDjsml4jptqyUcdixdqOlYvFRHI6OMT3yyI7MAG7uXG
	 v1o/I8n98n6xnmj6EdpQVtydJza825kQTq20GOIMojaFcqPrYLxc//ZVOMqv4WvwiR
	 3AmS4KRgMi7rhDNpKizRBdXA74Cuz71iDH4+w6TA=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of
 variable from named address space
Date: Tue, 28 May 2024 17:09:23 +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: 14.1.1
X-Bugzilla-Keywords: 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: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-115172-4-9rk5Dz7XlT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-115172-4@http.gcc.gnu.org/bugzilla/>
References: <bug-115172-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=3D115172

--- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Uros Bizjak <uros@gcc.gnu.or=
g>:

https://gcc.gnu.org/g:d8985ea10c911c994e00dbd6a08dcae907ebc1f7

commit r11-11454-gd8985ea10c911c994e00dbd6a08dcae907ebc1f7
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed May 22 09:12:28 2024 +0200

    ubsan: Use right address space for MEM_REF created for bool/enum
sanitization [PR115172]

    The following testcase is miscompiled, because -fsanitize=3Dbool,enum
    creates a MEM_REF without propagating there address space qualifiers,
    so what should be normally loaded using say %gs:/%fs: segment prefix
    isn't.  Together with asan it then causes that load to be sanitized.

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

            PR sanitizer/115172
            * ubsan.c (instrument_bool_enum_load): If rhs is not in generic
            address space, use qualified version of utype with the right
            address space.  Formatting fix.

            * gcc.dg/asan/pr115172.c: New test.

    (cherry picked from commit d3c506eff54fcbac389a529c2e98da108a410b7f)=