public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56009] New: Nested global destruction semantics not working (mingw)
Date: Wed, 16 Jan 2013 19:58:00 -0000	[thread overview]
Message-ID: <bug-56009-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56009
           Summary: Nested global destruction semantics not working
                    (mingw)
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: daniel.kruegler@googlemail.com


The following program - compiled with flags

-Wall -pedantic-errors

produces an unexpected output:

//-----------------------------------
extern "C" int printf(const char *, ...);

class A {
  A(const A&);
  A& operator=(const A&);
  A() { printf("A()\n"); }
  ~A() { printf("~A()\n"); }

public:
  void use() {
    printf("A is here!\n");
  }

  static A& get_instance() {
    static A result;
    return result;
  }
};

void use_A(const char* message) {
  A& a = A::get_instance();
  printf("Using A %s\n", message);
  a.use();
}

struct B {
  ~B() { use_A("from ~B()"); }
} b;

int main() {}
//-----------------------------------

A()
Using A from ~B()
A is here!

Note the lack of the expected last line:

~A()

Some further characteristics:

1) The problem is observed on a mingw-64bit system (Windows 7). I have been
told that the problem doesn't occur on Linux(?) systems (Thanks to Jonathan
Wakely)

2) The kind of global destruction semantics doesn't matter: Instead of a local
static variables we can use corresponding series of nested atexit()
registrations.

3) The problem is not related to flushing: Replacement of above printf calls by
e.g. std::cout with an effective std::flush call doesn't change anything


             reply	other threads:[~2013-01-16 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 19:58 daniel.kruegler at googlemail dot com [this message]
2013-01-21 10:46 ` [Bug c++/56009] " daniel.kruegler at googlemail dot com
2013-01-21 11:03 ` [Bug target/56009] " paolo.carlini at oracle dot com
2024-04-09  2:35 ` pinskia at gcc dot gnu.org
2024-04-09  2:38 ` pinskia 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-56009-4@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).