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 8B8843858C62; Thu,  1 Feb 2024 05:00:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8B8843858C62
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706763639;
	bh=bxTg6O0QyV5N38/p0nibR1oW/0CbS68wod66HTSFA34=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=sfaLt5er64qpqTLTIoJOMn73QP4411awTHHODo8kA18v83CXabJ0Z9iyNf5npfZwY
	 8ZZ5xaqhZ0jPpEhh4DZu0TYakeHrqXZR30YxdIhfqdNUwEcG51B+jUKJ/1KV+UzOS9
	 be0P2R1ik4JBkiRI1Ulg9uukfP5vRqrLOLikmZFY=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/113698] GNU OpenMP with OMP_PROC_BIND alters thread
 affinity in a way that negatively affects performance
Date: Thu, 01 Feb 2024 05:00:39 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-113698-4-S2j0gfSomG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113698-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=3D113698

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Actually I misread the testcase, because it looks like LLVM's libomp follows
the same as GCC's.

And it looks like the OpenMP spec is specific about that behavior too.=