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 150A23842582; Thu,  6 Jun 2024 06:11:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 150A23842582
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1717654310;
	bh=7PNjN2DfXhIC4UZ9z8iOsdCODiwXOY1HHFWw3e3N5V8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pc0mlg/h1OVoHSSVnvcVv2JYXIEmTVcQyYzESJvg0154R95ICm3QxeKkab32DCWtq
	 u0E9vh8Uh07GnigPqFZ/b4WH5CLkoOkZJitBnlyYpM66gfgdiHhyvGMTG3gPdfkKjg
	 lhyygzuXV6nFCp+Rad87ysAKinuR4ubRsHKUVulk=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 15.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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-115367-4-HaslGNmXDG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-115367-4@http.gcc.gnu.org/bugzilla/>
References: <bug-115367-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=3D115367

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Niklas Hamb=C3=BCchen 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.=