public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-113698-4-S2j0gfSomG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113698-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113698

--- 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.

  parent reply	other threads:[~2024-02-01  5:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  4:48 [Bug libgomp/113698] New: " kugan at gcc dot gnu.org
2024-02-01  4:58 ` [Bug libgomp/113698] " pinskia at gcc dot gnu.org
2024-02-01  5:00 ` pinskia at gcc dot gnu.org [this message]
2024-02-01  8:36 ` jakub at gcc dot gnu.org
2024-02-09 20:31 ` kugan at gcc dot gnu.org
2024-02-09 20:40 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-113698-4-S2j0gfSomG@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).