public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stijn.deweirdt at ugent dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/114765] linking to libgomp and setting CPU_PROC_BIND causes affinity reset
Date: Thu, 18 Apr 2024 11:58:43 +0000	[thread overview]
Message-ID: <bug-114765-4-5hHD7tWSJK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114765-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Stijn De Weirdt <stijn.deweirdt at ugent dot be> ---
hi jakub,

apologies for my ignorance, but how is working as expected? i can't make this
up from the description of the variable; and it's unexpected since there is no
openmp code being run (naively then; clearly libgomp does something).

we have an environment where we set OMP_PROC_BIND=true because openmp code
clearly benefits from it; but it also affects code where libgomp is simply
linked to it, but nothing else is done with it.

if i would understand why or what libgomp does, i might be able to find some
workaround.

many thanks,

stijn

  parent reply	other threads:[~2024-04-18 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 11:31 [Bug libgomp/114765] New: " stijn.deweirdt at ugent dot be
2024-04-18 11:38 ` [Bug libgomp/114765] " jakub at gcc dot gnu.org
2024-04-18 11:58 ` stijn.deweirdt at ugent dot be [this message]
2024-04-18 12:02 ` jakub at gcc dot gnu.org
2024-04-18 12:19 ` stijn.deweirdt at ugent dot be
2024-04-18 14:01 ` amonakov at gcc dot gnu.org
2024-04-18 14:22 ` jakub at gcc dot gnu.org
2024-04-18 17:00 ` 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-114765-4-5hHD7tWSJK@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).