public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "E dot Kuemmerle at fz-juelich dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/33435] internal compiler error with templates and openmp
Date: Wed, 19 Sep 2007 09:40:00 -0000	[thread overview]
Message-ID: <20070919094026.12520.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33435-15097@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from E dot Kuemmerle at fz-juelich dot de  2007-09-19 09:40 -------
Here is a self-contained example:

template<class T, int Sz>
class Vector {
public:
  explicit Vector() {}
  ~Vector() {}
private:
  T                                             m_data[Sz];
};

int main() {
  Vector<int,3> a[10];
  int i;
#pragma omp parallel
  {
#pragma omp for schedule(dynamic)
    for (i=0; i<10; ++i) {
      // do something
    }
#pragma omp master
    {
        a[0] = a[1];
    }
#pragma omp for schedule(dynamic)
    for (i=0; i<10; ++i) {
      // do something
    }
  }
}

I can avoid the internal compiler error by:
 1) removing the '-fopenmp' option
 2) changing the '#pragma omp' statements as shown in the original example
 3) removing the destructor '~Vector() {}' from 'class Vector' in the new
example!


-- 


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


  parent reply	other threads:[~2007-09-19  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 12:48 [Bug c++/33435] New: " E dot Kuemmerle at fz-juelich dot de
2007-09-18 19:16 ` [Bug c++/33435] " bangerth at dealii dot org
2007-09-19  9:40 ` E dot Kuemmerle at fz-juelich dot de [this message]
2007-09-23 17:21 ` bangerth at dealii dot org
2008-03-12 14:46 ` E dot Kuemmerle at fz-juelich dot de
2008-06-16 15:04 ` bangerth at dealii dot org
2008-06-17 14:07 ` E dot Kuemmerle at fz-juelich dot de
2008-06-18  7:21 ` E dot Kuemmerle at fz-juelich dot de

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=20070919094026.12520.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).