Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Dec 2011 19:34:12 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Ed Schouten <ed@80386.nl>, 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:  <20120101033412.GB62729@troutmask.apl.washington.edu>
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
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 <sgk@troutmask.apl.washington.edu>, 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, could you write such bug reports yourself? I am really
> > not that interested in GCC's development process.
> 
> 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...

I've already sent a patch to GCC to work around the problem.
FreeBSD is still considered to be a primary platform for GCC, 
so problem is a P1 issue in bugzilla.  Unfortunately, I think
that there are no active FreeBSD gcc maintainer.  This means
the patch may linger in bugzilla for awhile.

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120101033412.GB62729>