public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wwwhhhyyy333 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/109062] New: [13 regression] Default value of GOMP_SPINCOUNT changes since r13-2545
Date: Wed, 08 Mar 2023 03:23:43 +0000	[thread overview]
Message-ID: <bug-109062-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109062
           Summary: [13 regression] Default value of GOMP_SPINCOUNT
                    changes since r13-2545
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wwwhhhyyy333 at gmail dot com
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---

Recently we found several big regressions on Phoronix OpenMP benchmark on
GCC13. The regressions is caused by r13-2545-g9f2fca56593a2b

The issue is, the default value of GOMP_SPINCOUNT is now 0, instead of 300000
before this patch, which caused all Openmp program behaves like
OMP_WAIT_POLICY=passive.

As the comments in libgomp/env.c says:

 /* Using a rough estimation of 100000 spins per msec,
    use 5 min blocking for OMP_WAIT_POLICY=active,
    3 msec blocking when OMP_WAIT_POLICY is not specificed
    and 0 when OMP_WAIT_POLICY=passive.
    Depending on the CPU speed, this can be e.g. 5 times longer
    or 5 times shorter.  */

The current code for wait_policy is

if (none != NULL && gomp_get_icv_flag (none->flags, GOMP_ICV_WAIT_POLICY))
  wait_policy = none->icvs.wait_policy;
else if (all != NULL && gomp_get_icv_flag (all->flags, GOMP_ICV_WAIT_POLICY))
  wait_policy = all->icvs.wait_policy;

If OMP_WAIT_POLICY not specified, non of the branch will be entered since
gomp_get_icv_flag will return 0 by default, then wait_policy remains its value
as uninitialized. While prior to this patch wait_policy will be set to -1 (not
specified) by parse_wait_policy ().

             reply	other threads:[~2023-03-08  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  3:23 wwwhhhyyy333 at gmail dot com [this message]
2023-03-08  7:51 ` [Bug libgomp/109062] " rguenth at gcc dot gnu.org
2023-03-09  1:01 ` cvs-commit at gcc dot gnu.org
2023-03-09  1:07 ` wwwhhhyyy333 at gmail dot com

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