public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spollmann at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33581]  New: OpenMP segmentation fault
Date: Fri, 28 Sep 2007 08:15:00 -0000	[thread overview]
Message-ID: <bug-33581-15162@http.gcc.gnu.org/bugzilla/> (raw)

The following code (a general case) generates a segmentation fault when
compiled with the -m32 and -fopenmp switch in gcc 4.2.1.  With the -m32 switch
removed, the program executes correctly.

#include <iostream>

int main()
{
  int x;

#pragma omp parallel for
  for (x = 0; x < 100; x++)
    {
      std::cout << x << std::endl;
    }
  return 0;
}

compile command line: /usr/local/gcc-4.2.1/bin/g++ --static -fopenmp -m32 -o
openMPTestProgram openMPTest.cpp

System:  SUSE 10 x64 linux distribution, 
(Dual-core Intel(R) Pentium(R) D CPU 2.80GHz system), 4GB ram

GCC configuration option: ../gcc-4.2.1/configure --prefix=/usr/local/gcc-4.2.1


-- 
           Summary: OpenMP segmentation fault
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: spollmann at gmail dot com


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


             reply	other threads:[~2007-09-28  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  8:15 spollmann at gmail dot com [this message]
2007-09-28  8:22 ` [Bug c++/33581] " spollmann at gmail dot com
2007-09-28  9:36 ` [Bug middle-end/33581] " pinskia at gcc dot gnu dot org
2007-09-28  9:36 ` pinskia at gcc dot gnu dot org
2007-09-29  7:04 ` spollmann at gmail dot com
2007-09-29  7:10 ` spollmann at gmail dot com
2007-09-29  8:50 ` pinskia at gcc dot gnu dot org
2007-10-26  6:49 ` jakub at gcc dot gnu dot 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-33581-15162@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).