public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/115367] The implementation of OMP_DYNAMIC is not dynamic
Date: Thu, 06 Jun 2024 06:11:49 +0000	[thread overview]
Message-ID: <bug-115367-4-HaslGNmXDG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115367-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Niklas Hambüchen from comment #0)
> Those docs sound like the behaviour is nice "runtime-dynamic" when in fact
> it is fixed across the process's liftime, and based on ultra-slow rolling
> averages.

That is not the case.  It really calls getloadavg each time when trying to
determine the number of threads and uses the 15min average then.
Using say 1min average is IMHO highly undesirable for decisions in a program
that usually will last longer than that.

  reply	other threads:[~2024-06-06  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  1:59 [Bug libgomp/115367] New: " mail+gcc at nh2 dot me
2024-06-06  6:11 ` jakub at gcc dot gnu.org [this message]
2024-06-06  7:13 ` [Bug libgomp/115367] " comptes at ugo235 dot fr
2024-06-06  7:43 ` comptes at ugo235 dot fr

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-115367-4-HaslGNmXDG@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).