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/58691] OpenMP 4: Surprising results with OMP_PLACES=
Date: Sat, 12 Oct 2013 07:52:00 -0000	[thread overview]
Message-ID: <bug-58691-4-U2xiWDYbIc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58691-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58691

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Oct 12 07:52:15 2013
New Revision: 203479

URL: http://gcc.gnu.org/viewcvs?rev=203479&root=gcc&view=rev
Log:
    PR libgomp/58691
    * config/linux/proc.c (gomp_cpuset_popcount): Add unused attribute
    to check variable.
    (gomp_init_num_threads): Move i variable declaration into
    #ifdef CPU_ALLOC_SIZE block.
    * config/linux/affinity.c (gomp_affinity_init_level): Test
    gomp_places_list_len == 0 rather than gomp_places_list == 0
    when checking for topology reading error.
    * team.c (gomp_team_start): Don't handle bind == omp_proc_bind_false.
    * env.c (parse_affinity): Add ignore argument, if true, don't populate
    gomp_places_list, only parse env var and always return false.
    (parse_places_var): Likewise.  Don't check gomp_global_icv.bind_var.
    (initialize_env): Always parse OMP_PLACES and GOMP_CPU_AFFINITY env
    vars, default to OMP_PROC_BIND=true if OMP_PROC_BIND wasn't specified
    and either of these variables were parsed correctly into a places
    list.

Modified:
    trunk/libgomp/ChangeLog
    trunk/libgomp/config/linux/affinity.c
    trunk/libgomp/config/linux/proc.c
    trunk/libgomp/env.c
    trunk/libgomp/team.c


      parent reply	other threads:[~2013-10-12  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 20:03 [Bug libgomp/58691] New: " burnus at gcc dot gnu.org
2013-10-11 22:17 ` [Bug libgomp/58691] " jakub at gcc dot gnu.org
2013-10-12  7:16 ` burnus at gcc dot gnu.org
2013-10-12  7:50 ` jakub at gcc dot gnu.org
2013-10-12  7:52 ` jakub at gcc dot gnu.org [this message]

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