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 258A5385841C; Fri, 19 Jan 2024 15:41:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 258A5385841C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705678892;
	bh=erMzCFRMZeV8LrOWRTw0l/vI5Eda3B9JHJlYmHpSH+o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=U3UM80qpjqLTpekAxEaw617vAj1VCGD8pMinPCYtSHV1cA48foFGAC3ZSShO8ciAO
	 akZNFhCGwXN1nrIlJu2jrFnWU5+5nYYYOf1H1k8HGfgeA1aDU08W2ClgyDDWdp25Px
	 XaSU5JdFdGFpnlfz8FCEmwKtXXgmYnrosKwSWxwU=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113504] High memory usage for parallel `std::sort`
Date: Fri, 19 Jan 2024 15:41:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 12.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113504-4-nVbT6DX80m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113504-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113504-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=3D113504

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The parallel algos are taken from
https://github.com/llvm/llvm-project/tree/main/pstl so I would file an issue
upstream rather than here. The Intel PSTL developers are the right people to
ask.=