NSDMI bug?

2011-12-23 Thread Miles Bader
Is the following code valid? #include struct X { std::tuple tt{1, 2}; // works }; struct Y { std::tuple tt = std::tuple{1, 2}; // *error* }; 'cause it results in an error with gcc 20111210: $ g++-snapshot -c -std=c++11 nsdmi2.cc nsdmi2.cc:10:43: error:

Re: NSDMI bug?

2011-12-23 Thread Jonathan Wakely
On 23 December 2011 09:06, Miles Bader wrote: > Is the following code valid? > >   #include > >   struct X >   { >     std::tuple tt{1, 2};   // works >   }; > >   struct Y >   { >     std::tuple tt = std::tuple{1, 2};   // *error* >   }; > > 'cause it results in an error with gcc 20111210: > >  

Re: NSDMI bug?

2011-12-23 Thread Miles Bader
k, bugzilla'd thanks, -miles -- Cat is power.  Cat is peace.

gcc-4.6-20111223 is now available

2011-12-23 Thread gccadmin
Snapshot gcc-4.6-20111223 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20111223/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

non-virtual-destructor warnings redux

2011-12-23 Thread Miles Bader
gcc seems to have had a succession of warnings about non-virtual- destructors-in-classes-with-virtual-methods, none of which really worked all that well in practice (and so none are enabled by default, even by -Wall or -Wextra). But I notice clang has a variant which seems pretty well-behaved on r