public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geir at cray dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/33720] A negative value in OpenMP clause num_threads is not detected at runtime
Date: Mon, 14 Sep 2009 20:00:00 -0000	[thread overview]
Message-ID: <20090914195945.14051.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33720-13968@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from geir at cray dot com  2009-09-14 19:59 -------
(In reply to comment #4)
> Geir, have you run the testcase with other compilers? What is the result?
> 

Changed test cast to use 2 threads ("omp_set_num_threads(2);")

  PGI 9.0-3

$ pgcc -mp bug2883.c
$ ./a.out
pi       3.1416 n_thread -7
Error: omp_set_num_threads value (-7) is invalid
$

  Pathscale 3.2.99:

$ pathcc -mp bug2883.c
$ ./a.out
pi       3.1416 n_thread -7
actual_num_threads = 1
$

  Intel/11.1.046:

$ icc -openmp bug2883.c
$ ./a.out
pi       3.1416 n_thread -7
actual_num_threads = 2
$

  Cray 7.1.3:

$ cc -target=native bug2883.c
$ ./a.out
pi       3.1416 n_thread -7
actual_num_threads = 2
$

$


-- 


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


  parent reply	other threads:[~2009-09-14 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 20:49 [Bug c/33720] New: A negative value in OpenMP clause num_threasds " geir at cray dot com
2007-10-09 23:28 ` [Bug libgomp/33720] " bkoz at gcc dot gnu dot org
2007-11-12 19:37 ` [Bug libgomp/33720] A negative value in OpenMP clause num_threads " jakub at gcc dot gnu dot org
2008-08-07  2:56 ` manu at gcc dot gnu dot org
2009-07-31 15:12 ` manu at gcc dot gnu dot org
2009-09-14 20:00 ` geir at cray dot com [this message]
     [not found] <bug-33720-4@http.gcc.gnu.org/bugzilla/>
2013-06-19 18:19 ` geir at cray dot com
2013-06-19 18:23 ` jakub at gcc dot gnu.org
2013-06-19 20:45 ` manu at gcc dot gnu.org
2021-12-29  7:54 ` 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=20090914195945.14051.qmail@sourceware.org \
    --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).