public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bbenin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48869] New: OpenMP task construct fails to instantiate copy constructor(same as Bug 36523)
Date: Wed, 04 May 2011 13:04:00 -0000	[thread overview]
Message-ID: <bug-48869-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: OpenMP task construct fails to instantiate copy
                    constructor(same as Bug 36523)
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: bbenin@gmail.com


The same bug like in gcc 4.4.0 Bug 36523.
The following test case fails with a linker error. It compiles okay with the
pragma omp task line removed.

$ cat task.cpp 
template<typename T>
struct A
{
  A() { }
  A(const A&) { }
  void foo() { }
};

int main()
{
  A<int> a;
  #pragma omp task
    a.foo();
  return 0;
}

$ g++ -fopenmp -Wall task.cpp 
/tmp/cc5epalM.o: In function `main.omp_cpyfn.1':
task.cpp:(.text+0x73): undefined reference to `A<int>::A(A<int> const&)'
collect2: ld returned 1 exit status

$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/lto-wrapper
Target: x86_64-linux-gnu
.......
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)


             reply	other threads:[~2011-05-04 13:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 13:04 bbenin at gmail dot com [this message]
2011-05-04 13:07 ` [Bug c++/48869] " paolo.carlini at oracle dot com
2011-05-04 15:40 ` jakub at gcc dot gnu.org
2011-05-04 15:57 ` [Bug c++/48869] [4.5/4.6/4.7 Regression] " jakub at gcc dot gnu.org
2011-05-04 15:58 ` rguenther at suse dot de
2011-05-04 16:31 ` jakub at gcc dot gnu.org
2011-05-04 16:41 ` jakub at gcc dot gnu.org
2011-05-04 18:00 ` jason at gcc dot gnu.org
2011-05-11  8:23 ` jakub at gcc dot gnu.org
2011-05-19  8:16 ` jakub at gcc dot gnu.org
2011-05-19  8:25 ` [Bug c++/48869] [4.5 " jakub at gcc dot gnu.org
2011-05-19  8:48 ` [Bug c++/48869] [4.5/4.6/4.7 " jakub at gcc dot gnu.org
2011-08-01 13:58 ` [Bug c++/48869] [4.5 " rguenth at gcc dot gnu.org
2012-07-02 10:50 ` rguenth 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-48869-4@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).