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 BD2563856DE8; Fri, 28 Jul 2023 05:12:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD2563856DE8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690521169;
	bh=T8MxpUMwruZ4/U0XKcJY+o6KGONYNcQ6oJyd9be6LpI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qo53etMqbRxaGgR+Tu1IvNY91/EylWMSfcWvYMEci+qNyiHmptTBKA2xVex0PRSWI
	 owokjINK3R8iqtRJQIz3xiH5suyRWM3cBCs3S7+Xow1mfxH1M4kXQ/RKXnsSBfN6pD
	 OIqD6j7ClXxyH0Avu8lIGH7YZYj7PHpz2kl/r+pA=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/110835] [13/14 Regression] -fsanitize=address causes
 huge runtime slowdown from std::rethrow_exception not called
Date: Fri, 28 Jul 2023 05:12:49 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110835-4-i2iNAkDzbg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110835-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=3D110835

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Which might mean it is an issue in LLVM too ...
>=20
> Yes the same runtime regression shows up between clang 15 and clang 16. T=
his
> should reported upstream to them too.

What is interesting is that with -stdlib=3Dlibc++ the regression for clang/=
LLVM
shows up between their 14 and 15 releases.

Anyways this should be filed upstream ...=