public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/24847] Instantiates un-called copy constructor
Date: Wed, 23 Nov 2005 05:21:00 -0000	[thread overview]
Message-ID: <20051123052100.30187.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24847-6594@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from bangerth at dealii dot org  2005-11-23 05:21 -------
The second constructor is definitely bogus, but its mere existence 
does no harm. We should only perform the check for sensibility when
we actually instantiate the second constructor.

W.


-- 

bangerth at dealii dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-11-23 05:21:00
               date|                            |


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


  parent reply	other threads:[~2005-11-23  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 14:06 [Bug c++/24847] New: " igodard at pacbell dot net
2005-11-14 19:32 ` [Bug c++/24847] " pinskia at gcc dot gnu dot org
2005-11-15  0:30 ` igodard at pacbell dot net
2005-11-23  5:21 ` bangerth at dealii dot org [this message]
     [not found] <bug-24847-4@http.gcc.gnu.org/bugzilla/>
2021-08-01 23:30 ` pinskia at gcc dot gnu.org
2021-08-02  9:11 ` redi at gcc dot gnu.org
2021-08-02  9:14 ` redi 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=20051123052100.30187.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).