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 15E3A3858C50; Sun, 30 Apr 2023 18:40:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 15E3A3858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1682880048;
	bh=+XRygsPjag7tOAnGHn2VUQf3Eq4TJFFc3VcjiSwNO4E=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Z1y9zI7CBVh/HFSNfqj/uwCYb1+eBr6FKNbnbO4Lm8SxXZG7VgtpwmkfLAL/uHiqo
	 J2P28sC/aoofXJ7vME8k3IJUVH+tRKUdjXkf4sVQ3KoUzB6yrhXKdwOkXPnJGBKwVE
	 ooZr3MBAAlX56UTJhYIAhv1tjyW33pXQ0VmnyFZk=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109674] [14 Regression] linking with libhwasan is now
 broken
Date: Sun, 30 Apr 2023 18:40:47 +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.0
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109674-4-L4peidss0C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109674-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=3D109674

--- Comment #5 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
The solution is probably very similar to libasan library where also __lsan
symbols are used and where we link against ../lsan/.libs/libsanitizer_lsan.=
a.=