public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10112: static data member is not correctly initialized Date: Tue, 18 Mar 2003 02:46:00 -0000 [thread overview] Message-ID: <20030318024600.32178.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10112; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: "Giovanni Bajo" <giovannibajo@libero.it> Cc: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>, <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <o.kullmann@swansea.ac.uk>, <nathan@gcc.gnu.org> Subject: Re: c++/10112: static data member is not correctly initialized Date: 18 Mar 2003 03:34:23 +0100 "Giovanni Bajo" <giovannibajo@libero.it> writes: | ----- Original Message ----- | From: "Gabriel Dos Reis" <gdr@integrable-solutions.net> | To: "Giovanni Bajo" <giovannibajo@libero.it> | Cc: "Wolfgang Bangerth" <bangerth@ticam.utexas.edu>; | <gcc-gnats@gcc.gnu.org>; <gcc-bugs@gcc.gnu.org>; <o.kullmann@swansea.ac.u= k>; | <nathan@gcc.gnu.org> | Sent: Tuesday, March 18, 2003 2:46 AM | Subject: Re: c++/10112: static data member is not correctly initialized |=20 |=20 | >From which parts of the standard did read that? |=20 | I was reading =A73.6.2p1 <<before any other initialization takes place>> = in | this way. That paragraph speaks about initialisation of objects. It says nothing about the order of template instantiations and the order | Anyway, the bug is about the order of initialization between two static d= ata | members. Since instantiation of class templates does not affect | initialization of static data members (as per quoted paragraph), even if = you | instantiate the class templates before inizializing the data members, you | should respect the order of inizialization of the data members. Unless the instantiation of the class template uses the static data members.=20 | It seems to me that GCC is initializing the static data members because t= he | templates are instantiated, but this violates =A714.7.1p8. What you're missing is that your expression in the assertion introduces an indeterminism in the order of instantiation. It is the instantiation of the static data members that defines them, not just their mere -template- definition. What is happening is not far from the following scenario:=20 struct A {=20 int p; =20 A(int x) : p(x) { } };=20 struct B { static A a; static int p1; }; int B::p1 =3D a.p; A B::a(123); int main() { assert (B::a.p =3D=3D B::p1); }=20 -- Gaby
next reply other threads:[~2003-03-18 2:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-18 2:46 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-18 2:06 Giovanni Bajo 2003-03-18 1:56 Gabriel Dos Reis 2003-03-18 1:46 Giovanni Bajo 2003-03-18 0:16 Wolfgang Bangerth
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=20030318024600.32178.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).