public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: norbert@spice.gia.rwth-aachen.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/7466: gcc does not create a destructor call for a temporary
Date: Thu, 01 Aug 2002 09:56:00 -0000	[thread overview]
Message-ID: <20020801165423.14274.qmail@sources.redhat.com> (raw)


>Number:         7466
>Category:       c++
>Synopsis:       gcc does not create a destructor call for a temporary
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 01 09:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Norbert Berzen
>Release:        gcc version 3.1
>Organization:
>Environment:
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: /WINEXPORT/DEVEL/gcc-x.y.z/gcc-3.1/configure --prefix=/usr
Thread model: single
gcc version 3.1
>Description:
gcc does not create a destructor call for a temporary
object which has a non-trivial destructor.
When xxx.cpp is compiled using "g++ -o xxx xxx.cpp"
then only C() is called, and ~C() is not called at all.
But when xxx.cpp is compiled by "g++ -O3 -o xxx xxx.cpp"
then C() gets called once as well as ~C() gets called
once.
>How-To-Repeat:
Compile xxx.cpp by "g++ -o xxx xxx.cpp" and run the program.
Compile it by "g++ -O3 -o xxx xxx.cpp" and run the program.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="xxx.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="xxx.cpp"

LyoKICogRmlsZTogeHh4LmNwcAogKi8KCmV4dGVybiAiQyIgaW50IHByaW50ZiAoLi4uKTsKCnN0
cnVjdCBDIHsKICBDICgpIHsgcHJpbnRmICgiQyAoKVxuIik7IH0KICB+QyAoKSB7IHByaW50ZiAo
In5DICgpXG4iKTsgfQp9OwoKc3RhdGljIGNvbnN0IEMgZiAodm9pZCkKewogIHJldHVybiBDKCk7
Cn0KCnN0YXRpYyB2b2lkIGcgKEMgaW5fYykKewogIC8qIGVtcHR5ICovCn0KCmludAptYWluICgp
CnsKICBnIChmICgpKTsKICByZXR1cm4gMDsKfQoKCi8qCiAqIFRoaXMgcHJvZHVjZXMgd3Jvbmcg
Y29kZTogICAiZysrIC1vIHh4eCB4eHguY3BwIgogKgogKiBUaGF0IHByb2R1Y2VzIGNvcnJlY3Qg
Y29kZTogImcrKyAtTzMgLW8geHh4IHh4eC5jcHAiCiAqLwo=


             reply	other threads:[~2002-08-01 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-01  9:56 norbert [this message]
2002-09-13 14:58 nathan
2002-09-16 12:19 nathan

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=20020801165423.14274.qmail@sources.redhat.com \
    --to=norbert@spice.gia.rwth-aachen.de \
    --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).