public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ahelm@gmx.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/6803: Default copy constructor problem in GCC v3.1
Date: Fri, 24 May 2002 13:46:00 -0000 [thread overview]
Message-ID: <20020524195311.30228.qmail@sources.redhat.com> (raw)
>Number: 6803
>Category: c++
>Synopsis: Default copy constructor problem in GCC v3.1
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri May 24 12:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Anton Helm
>Release: 3.1
>Organization:
>Environment:
DJGPP
>Description:
Code compiles with GCC v2.95.2, v2.95.3,
v3.0.2, v3.0.3 and v3.0.4 but not with v3.1.
copy_problem.cpp: In copy constructor `QQ::QQ(const QQ&)':
copy_problem.cpp:57: invalid conversion from `const RR*' to `long long int'
copy_problem.cpp:57: initializing argument 1 of `RR::RR(long long int)'
copy_problem.cpp: In function `int main()':
copy_problem.cpp:57: initializing temporary from result of `QQ::QQ(const RR&
>How-To-Repeat:
compile with g++ v3.1, e.g.
g++ copy_problem.cpp
>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="copy_problem.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="copy_problem.cpp"
Y2xhc3MgUVE7DQoNCmNsYXNzIFJSDQp7IA0KcHVibGljOg0KICBzaG9ydCB4eDsNCiAgICAgICAg
UlIoY29uc3QgbG9uZyBsb25nIGkpOw0KICAgICAgICBSUigpOw0KICAgICAgICBSUihjb25zdCBS
UiYgZik7DQogICAgICAgIH5SUigpOw0KfTsNCg0KY2xhc3MgUVENCnsNCnB1YmxpYzoNCiAgUlIg
ICAgeXlbNF1bNF07DQogICAgICAgIFFRKCk7DQogICAgICAgIFFRKGNvbnN0IFJSJiBmKTsNCiAg
ICAgICAgflFRKCk7DQp9Ow0KDQppbmxpbmUgUlI6OlJSKGNvbnN0IGxvbmcgbG9uZyBpKQ0Kew0K
ICB4eCA9IChzaG9ydClpOw0KfQ0KDQppbmxpbmUgUlI6OlJSKCkge3h4ID0gMDt9DQppbmxpbmUg
UlI6OlJSKGNvbnN0IFJSJiBmKSB7eHggPSBmLnh4O30NCmlubGluZSBSUjo6flJSKCkge30NCg0K
aW5saW5lIFFROjpRUSgpDQp7DQogIGZvcihpbnQgaT0wO2k8NDtpKyspDQogIHsNCiAgICBmb3Io
aW50IGo9MDtqPDQ7aisrKQ0KICAgIHsNCiAgICAgIHl5W2ldW2pdID0gMDsNCiAgICB9DQogIH0N
Cn0NCg0KaW5saW5lIFFROjpRUShjb25zdCBSUiAmZikNCnsNCiAgZm9yKGludCBpPTA7aTw0O2kr
KykNCiAgew0KICAgIGZvcihpbnQgaj0wO2o8NDtqKyspDQogICAgew0KICAgICAgeXlbaV1bal0g
PSBmOw0KICAgIH0NCiAgfQ0KfQ0KDQppbmxpbmUgUVE6On5RUSgpe30NCg0KaW50IG1haW4oKQ0K
ew0KICBRUSB4ICA9IFJSKDEyMyk7DQogIFFRICp5ID0gJng7DQogIFFRIHogID0gKnk7DQoNCiAg
cmV0dXJuIHgueXlbM11bM10ueHg7DQp9DQo=
next reply other threads:[~2002-05-24 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 13:46 ahelm [this message]
2002-05-25 5:46 paolo
2002-06-17 7:06 lerdsuwa
2002-07-03 8:46 lerdsuwa
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=20020524195311.30228.qmail@sources.redhat.com \
--to=ahelm@gmx.net \
--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).