Re: svn commit: r228955 - head/include

2012-01-01 Thread David Schultz
On Sun, Jan 01, 2012, Ed Schouten wrote: > David, > > * David Schultz , 20120101 03:54: > > I'm out of town and don't remember the details of this, but is there a > > reason we couldn't simply have an appropriate #ifdef that uses > > __attribute((__noreturn__)) instead of [[noreturn]]? We have pl

Re: svn commit: r228955 - head/include

2012-01-01 Thread Ed Schouten
David, * David Schultz , 20120101 03:54: > I'm out of town and don't remember the details of this, but is there a > reason we couldn't simply have an appropriate #ifdef that uses > __attribute((__noreturn__)) instead of [[noreturn]]? We have plenty > of ifdefs in the tree already to work around d

Re: svn commit: r228955 - head/include

2011-12-31 Thread Steve Kargl
On Sat, Dec 31, 2011 at 09:54:22PM -0500, David Schultz wrote: > On Thu, Dec 29, 2011, Ed Schouten wrote: > > Hi Steve, > > > > * Steve Kargl , 20111229 19:49: > > > Are you going to submit a bug report to GCC? Because, as of now, > > > you've broken my ability to do development work on bleeding

Re: svn commit: r228955 - head/include

2011-12-31 Thread David Schultz
On Thu, Dec 29, 2011, Ed Schouten wrote: > Hi Steve, > > * Steve Kargl , 20111229 19:49: > > Are you going to submit a bug report to GCC? Because, as of now, > > you've broken my ability to do development work on bleeding edge > > freebsd and bleeding edge gcc. > > Here you go: > > http:/

Re: svn commit: r228955 - head/include

2011-12-29 Thread Steve Kargl
On Thu, Dec 29, 2011 at 08:23:59PM +0100, Ed Schouten wrote: > Hi Steve, > > * Steve Kargl , 20111229 19:49: > > Are you going to submit a bug report to GCC? Because, as of now, > > you've broken my ability to do development work on bleeding edge > > freebsd and bleeding edge gcc. > > Here you g

Re: svn commit: r228955 - head/include

2011-12-29 Thread Ed Schouten
Hi Steve, * Steve Kargl , 20111229 19:49: > Are you going to submit a bug report to GCC? Because, as of now, > you've broken my ability to do development work on bleeding edge > freebsd and bleeding edge gcc. Here you go: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51705 In the future,

Re: svn commit: r228955 - head/include

2011-12-29 Thread Steve Kargl
On Thu, Dec 29, 2011 at 07:32:13PM +0100, Ed Schouten wrote: > Hi Andreas, > > * Andreas Tobler , 20111229 18:43: > > Thank you Ed! gcc-4.6 bootstrap successful. > > But it seems GCC 4.7 is still broken. I am not planning to fix that, > because it's a shortcoming of GCC. As soon as the GNU folks

Re: svn commit: r228955 - head/include

2011-12-29 Thread Andreas Tobler
Hi Ed, On 29.12.11 19:32, Ed Schouten wrote: * Andreas Tobler, 20111229 18:43: Thank you Ed! gcc-4.6 bootstrap successful. But it seems GCC 4.7 is still broken. I am not planning to fix that, because it's a shortcoming of GCC. As soon as the GNU folks implement C++11 [[noreturn]], it should

Re: svn commit: r228955 - head/include

2011-12-29 Thread Ed Schouten
Hi Andreas, * Andreas Tobler , 20111229 18:43: > Thank you Ed! gcc-4.6 bootstrap successful. But it seems GCC 4.7 is still broken. I am not planning to fix that, because it's a shortcoming of GCC. As soon as the GNU folks implement C++11 [[noreturn]], it should work again. -- Ed Schouten WWW

Re: svn commit: r228955 - head/include

2011-12-29 Thread Andreas Tobler
On 29.12.11 15:41, Ed Schouten wrote: Author: ed Date: Thu Dec 29 14:41:17 2011 New Revision: 228955 URL: http://svn.freebsd.org/changeset/base/228955 Log: Don't define static_assert for C++. Even though _Static_assert() is pretty robust for C code, it cannot work correctly with C++ co

svn commit: r228955 - head/include

2011-12-29 Thread Ed Schouten
Author: ed Date: Thu Dec 29 14:41:17 2011 New Revision: 228955 URL: http://svn.freebsd.org/changeset/base/228955 Log: Don't define static_assert for C++. Even though _Static_assert() is pretty robust for C code, it cannot work correctly with C++ code. This is due to the fact that C++ tem