From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8D4AE3858CD1; Fri, 14 Jul 2023 10:06:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8D4AE3858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689329185; bh=YKA5ePFk7076OOhioctnZ7G85TLfGbr1Oq4Jf60IRPM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ybJSb9p6draxn0PSsSYI0uYV1aDWmYTILye0pvTMrCtOSfvgW6ApesCP91IVzVcAx YG85fbwfHE4v+bbyIZ0pF17x26uLETobc/e8fzcSlnQNk7+Zd4j/2ZcBE0luGugG4t ci9Ta1uHaIYIO2TpWNXslrpJoFbDOZdN6fnDIstk= From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/110663] [OpenMP] Use 'affinity' clause for node placement for the 'task' construct Date: Fri, 14 Jul 2023 10:06:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgomp X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: missed-optimization, openmp X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110663 --- Comment #1 from Tobias Burnus --- Carry on of Jakub's comment in PR99666 about implementing this: "Yeah, but not really sure if we want to do anything with it other than acc= ept it / verify the restrictions. "The tasking is already overly complicated and the right way is to make it = more scalable (have per thread task queues with work stealing rather than the 3 different queues we currently have with per-team lock)."=