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

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-04 16:25:46 UTC ---
Not sure if it would be ok to request instantiation of say copy ctor when we
are unsure if the var will be firstprivate or not.  The copy ctor can be marked
as =delete, or perhaps say the instantiation of the copy ctor could result in
static assertion failures or could use some =delete method...


  parent reply	other threads:[~2011-05-04 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 13:04 [Bug c++/48869] New: " bbenin at gmail dot com
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 [this message]
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-AIbadU3yhz@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).