[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2011-11-03 Thread richard-gccbugzilla at metafoo dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32534 Richard Smith richard-gccbugzilla at metafoo dot co.uk changed: What|Removed |Added CC|

[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2011-11-03 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32534 Jonathan Wakely redi at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2009-06-15 Thread jwakely dot gcc at gmail dot com
--- Comment #3 from jwakely dot gcc at gmail dot com 2009-06-15 09:19 --- (In reply to comment #0) I can't use template A Bint::a = something; form (which would help) because I have only empty ctor (like in the case of map). I'm not sure what you mean but this works fine: template

[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2009-06-15 Thread jwakely dot gcc at gmail dot com
--- Comment #4 from jwakely dot gcc at gmail dot com 2009-06-15 09:55 --- extern C int printf(const char*, ...); struct A { A() : value(1) { printf(A::A %d\n, value); } int value; }; templateclass T struct B { static A a; }; templateclass T A BT::a = A();

[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2009-06-11 Thread rodolfo at rodsoft dot org
--- Comment #1 from rodolfo at rodsoft dot org 2009-06-11 16:34 --- I've been bitten by this bug, which is almost 2 years old. I haven't tested it with gcc 4.4 though, but I confirm that it happens with gcc-4.3.3. Is there anyone willing to correct this? --

[Bug c++/32534] gcc fails to initialize template's static data members before their use in some cases

2009-06-11 Thread mikpe at it dot uu dot se
--- Comment #2 from mikpe at it dot uu dot se 2009-06-11 20:03 --- (In reply to comment #1) I've been bitten by this bug, which is almost 2 years old. I haven't tested it with gcc 4.4 though, but I confirm that it happens with gcc-4.3.3. Is there anyone willing to correct this?