public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bumgard@roguewave.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/2349: Compiler generated copy-constructor generates warning for unused argument.
Date: Thu, 22 Mar 2001 15:26:00 -0000	[thread overview]
Message-ID: <20010322231944.3808.qmail@sourceware.cygnus.com> (raw)

>Number:         2349
>Category:       c++
>Synopsis:       Compiler generated copy-constructor generates warning for unused argument.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 22 15:26:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Greg Bumgardner
>Release:        gcc 3.1 as of 2001-03-22
>Organization:
>Environment:
Redhat Linux 2.2.16
>Description:
Compiler generated copy-constructors produce warnings 
for unused argument if class has virtual destructor and
no members, and the compiler-generated copy-constructor 
is used to initialize an instance.

This problem seems to be very specific.
>How-To-Repeat:
c++ -W -Wall -Werror simple.cpp

produces:

cc1plus: warnings being treated as errors
simple.cpp: In method `Foo::Foo(const Foo&)':
simple.cpp:1: warning: unused parameter `const Foo&_ctor_arg'
>Fix:
Unknown.
This error was introduced sometime in the last month.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="simple.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="simple.cpp"

Y2xhc3MgRm9vIHsKICBwdWJsaWM6CiAgICB2aXJ0dWFsIH5Gb28odm9pZCkge30gLy8gV2Fybmlu
ZyByZXF1aXJlcyBleGlzdGFuY2Ugb2YgdmlydHVhbCBkZXN0cnVjdG9yIAp9OwoKY2xhc3MgQmFy
IHsKICBwdWJsaWM6CiAgICB+QmFyKHZvaWQpIHt9Cn07CgoKaW50IG1haW4oKSB7CgogIEZvbyBm
MTsKICBGb28gZjIoZjEpOyAvLyBHZW5lcmF0ZXMgd2FybmluZwogIEZvbyBmMyhGb28oKSk7IC8v
IERvZXMgbm90IGdlbmVyYXRlIHdhcm5pbmcKICAodm9pZClmMTsKICAodm9pZClmMjsKICAodm9p
ZClmMzsKCiAgQmFyIGIxOwogIEJhciBiMihiMSk7IC8vIERvZXMgbm90IGdlbmVyYXRlIHdhcm5p
bmcKICAodm9pZCliMTsKICAodm9pZCliMjsKICByZXR1cm4gMDsKfQo=


                 reply	other threads:[~2001-03-22 15:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010322231944.3808.qmail@sourceware.cygnus.com \
    --to=bumgard@roguewave.com \
    --cc=gcc-gnats@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).