public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "parviz_fariborz at mentor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/49231] #pragma omp parallel for never returns
Date: Mon, 30 May 2011 15:17:00 -0000	[thread overview]
Message-ID: <bug-49231-4-PDaYslEH9h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49231-4@http.gcc.gnu.org/bugzilla/>

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

Parviz Fariborz <parviz_fariborz at mentor dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |parviz_fariborz at mentor
                   |                            |dot com

--- Comment #2 from Parviz Fariborz <parviz_fariborz at mentor dot com> 2011-05-30 15:11:16 UTC ---


-Parviz(In reply to comment #1)
> Can't reproduce, tried gcc 4.4.5, 4.6 and 4.7, both -m32 and -m64, gcc and g++,
> and various options.

The compile/link option -static seems to be significant in this case. The
executable built with the following command :

/tools/linux64/gcc-4.4.3/bin/g++ -o omp -g -static -fopenmp -lgomp -lpthread
-I/tools/linux64/gcc-4.4.3/include -L/usr/lib64
-L/tools/linux64/gcc-4.4.3/lib64 omp.cc

Do not work. When I remove the -static option, it does work. Any ideas?


  parent reply	other threads:[~2011-05-30 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 13:05 [Bug libgomp/49231] New: " parviz_fariborz at mentor dot com
2011-05-30 14:09 ` [Bug libgomp/49231] " jakub at gcc dot gnu.org
2011-05-30 15:17 ` parviz_fariborz at mentor dot com [this message]
2011-05-30 16:40 ` jakub 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=bug-49231-4-PDaYslEH9h@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).