Date: Sun, 1 Jan 2012 10:29:25 +0100 From: Ed Schouten <ed@80386.nl> To: Steve Kargl <sgk@troutmask.apl.washington.edu>, Andreas Tobler <andreast@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r228955 - head/include Message-ID: <20120101092925.GZ1895@hoeg.nl> In-Reply-To: <20120101025422.GD94452@zim.MIT.EDU> References: <201112291441.pBTEfI8l060127@svn.freebsd.org> <4EFCA6A6.6080103@FreeBSD.org> <20111229183213.GK1895@hoeg.nl> <20111229184934.GA47885@troutmask.apl.washington.edu> <20111229192359.GM1895@hoeg.nl> <20120101025422.GD94452@zim.MIT.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
--N6OI5UwltL9FF6Nb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable David, * David Schultz <das@FreeBSD.ORG>, 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 deficiencies in various > compilers. Saying "it's the compiler's fault and we're not going to > work around it" is a significant departure from historical precedent, > and it punishes the wrong people. Easier than arguing with the GNU > folks about fixing it, too... Right now GCC 4.7 is still an unreleased piece of software. If GCC 4.7 was a released piece of software, I would of course agree that we should add the workaround. The problem isn't that GCC 4.7 doesn't support [[noreturn]]. The problem is that GCC only implements parts of C++11, yet it forces the compiler into C++11 mode while bootstrapping. Even if we add a workaround for this in sys/cdefs.h, we can likely never ever get rid of it. Because if someone wants to install GCC 4.7 on a FreeBSD 14.0 box in 2020 to build an old piece of software, he still needs the workaround. But there's nothing serious going on here. The issue is already discussed in GCC Bugzilla and there is a patch that fixes the build. Let's just wait to see what happens. --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --N6OI5UwltL9FF6Nb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQIcBAEBAgAGBQJPACd1AAoJEG5e2P40kaK7XUwP/1V1bGGtT9AnlJ9oX/ITiSu0 rTwOoSMGSPIN+xyilNPiJR30RaESAGPWhAwC2DmakUrFRw+mMmGlvkrlHv/cqKGu vZOWd+7tbOIShjEsEeOZZXVmAZXar7BtfKPhwpY/zGdiniOaLAAbFoa7yzCCMu1a xpUwgVC6SAGW2vik3jsqU0KFR+6iWVnw9U7CC5HiYkcUdJU2wdr/io7tz737t4iJ 8PhJh2t829Oh8oh4euZgHWi9yIjU4widD7poZX2TAtPVclDfFaDyWL5RTl2HNp8b rCqrNL/Mk/+Bu2fCcs2M2aynWA4CkbIi7EYFuiZkvdA5fXht8zie+0bDCTcbDk5v AGbylRSDy9QugueFmrk1nE7Ba5zYu9v+Jj2e2XYIqQuFsdPZljEgd9afDxmittQB gFpyrAaYikZMfr97V1+9L/ndk/0++9GnlcDXxkJtQ41vhb3Ar/8eq1zTC+nya1cc Wuw2fRqKet3f3zxTmy4VlOHOqMCCDhvYOhmy5JMYggur1PFHFqtVst7iwTTnO9Ut xUfds9BPB3Zd4cC+MjVHdtP4OknwrhveLCk/TeyxBJE3FHFwRvzi+hMcOgo4fZBN VLgWx1Grdr6OLomLZaXRNnK1WzaECQTapKfs2QHRGoexzy3+z2L6wtjkI85oYGpF L3D6F+hZpd8QRtsDI1IN =4pLG -----END PGP SIGNATURE----- --N6OI5UwltL9FF6Nb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120101092925.GZ1895>