From nobody Thu Nov 24 21:34:46 2022 X-Original-To: toolchain@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NJB922cH9z4jCK1 for ; Thu, 24 Nov 2022 21:34:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NJB921RT2z433f for ; Thu, 24 Nov 2022 21:34:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1669325686; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MdTNx7LXsBuaqV4yKM7GvFexLYWqx5IO/wROw0sxa20=; b=eGzMXrn8RRIZESP8TTfkYhQNTvhxHMNfQj4cf9C99hsMBiJCziwdYZIjj3GdGK96TFw1yO LRT7QtUOKwG/G+i+nOtCya0AyBbfqkHVOsXLvpudl1eqop1hCWt/F40TTgB9yc/O4difPB 0LbLtMoYTWrjYWaMzuE2YcD9xJ6Iu5DSwmc6h6N6jUqOKEyvFXy+2vqDP6eaEPpaNKCuUb Z0+b+Z6NkxILz/mO5HV9n6evUZnlEoOB+q8RGyFPom0JJoX+vzO7sFyrwWRLGHE7mh9pMi nztAK5NqyPpzSbCbtrkwl68iCwOZqo2QFpZ2X8O0xaGhDsICULRSPi24Fwal8g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1669325686; a=rsa-sha256; cv=none; b=a6aykMDVgyIqsogZeeZdJHWkLECyGplItsIromaJeqiBlJmd8TuJu2+kXs8rHiYS/sKwd/ KRkqEVHjLI91FJrvqZrNcNdNsiFgBkyDgc0fPOXbkrIbXfrLpZhkkkCwu9jptjPzUG0/jq 4cii3A+6UZ/jZrh4RTU5qy/t5EfxYUHFHQfl3IfjmGy3nBSm3D1UsQ6cF6D2sc/ClG/MJm LNAR9GnHOdOAWBuzCob8xcR1s9fMEPWSzocnhDa7RLg0CJhWyD3u4h/3cxLJiUM8XY3QUA weOFAWVzWQ66ZiV0rDXq407w4N2fQsbXzskO0Aq14rrRr40cgMU3yWg3X35/0w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4NJB920NZqzGrn for ; Thu, 24 Nov 2022 21:34:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 2AOLYjJe098307 for ; Thu, 24 Nov 2022 21:34:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 2AOLYjTb098306 for toolchain@FreeBSD.org; Thu, 24 Nov 2022 21:34:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 267751] lang/gcc*: Address sanitizer isn't properly enabled: ASan runtime does not come first in initial library list Date: Thu, 24 Nov 2022 21:34:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: salvadore@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: salvadore@freebsd.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Maintenance of FreeBSD s integrated toolchain List-Archive: https://lists.freebsd.org/archives/freebsd-toolchain List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267751 --- Comment #9 from Lorenzo Salvadore --- I have tested successfully the patch for gcc12-devel too. However, the patch for gcc13-devel does not seem to be completely successful: the compiled bin= ary starts, but it stops immediately with the following error from ASan. AddressSanitizer:DEADLYSIGNAL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D83034=3D=3DERROR: AddressSanitizer: BUS on unknown address (pc 0x0008= 017ae145 bp 0x00000001445a sp 0x7fffffffafc8 T0) =3D=3D83034=3D=3DThe signal is caused by a READ memory access. =3D=3D83034=3D=3DHint: this fault was caused by a dereference of a high val= ue address (see register values below). Disassemble the provided pc to learn which register was used. #0 0x8017ae145 (/lib/libc.so.7+0x159145) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: BUS (/lib/libc.so.7+0x159145)=20 =3D=3D83034=3D=3DABORTING I am doing my tests by compiling the following code: #include using namespace std; int main() { cout << "Hello world!"; return 0; } I still have to study what this error means, if it is one more bug indipend= ent from the one we are fixing in this PR, if this is an expected issue in the = HEAD of the GCC development or whatelse. If anyone already knows something about= it, help is welcome. In the meantime, here is the commit schedule for the other gcc ports: - the commits for gcc11-devel and gcc12-devel will be done within the week together with the updates to the latest snapshots; - the commit for gcc12 will be done after the gcc11-devel and gcc12-devel commits but before the commit of the GCC_DEFAULT update, which should be do= ne soon: indeed the exp run for it (bug #265948) has only one last known issue (bug #266189) for which I have already submitted a patch to the maintainer (which is you Yuri, but as you have probably seen it is only a USE_GCC=3D11 patch, so you might want to find a better solution); - the commit for gcc11 will be done after the GCC_DEFAULT update. I have built this schedule with the goal to reduce the gcc builds for users that only need GCC_DEFAULT: with this plan, they should only need to build gcc12 once and no gcc11. --=20 You are receiving this mail because: You are on the CC list for the bug.=