Date: Fri, 30 Nov 2012 12:13:31 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Eitan Adler <eadler@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: svn commit: r243670 - head/share/man/man5 Message-ID: <20121130121105.W1707@besplex.bde.org> In-Reply-To: <CAF6rxgkUVrWbOU2i2=16St1iyWJskeULpWjDT5hEZi0aX%2BsHCQ@mail.gmail.com> References: <201211291251.qATCpA7w078277@svn.freebsd.org> <20121130110154.E1441@besplex.bde.org> <CAF6rxgkUVrWbOU2i2=16St1iyWJskeULpWjDT5hEZi0aX%2BsHCQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Nov 2012, Eitan Adler wrote: > On 29 November 2012 19:09, Bruce Evans <brde@optusnet.com.au> wrote: >> On Thu, 29 Nov 2012, Eitan Adler wrote: > >> "gcc" was mostly correct here, since the flags are unportable gcc ones. >> They don't work with any "cc", but may work with clang, although this >> is unclear since none of them is documented in clang(1). > > Every time I talk to the clang folk about flags they point me to gcc > documentation. That's where I look too. It doesn't cover clang extensions. >> However, I never would have agreed to putting any of them here. >> >> Lots here is now superseded by flags set by WARNS anyway. >> >> clang's even more unportable new flags are not documented in clang(1) >> and the settings here are too old to have dreamed of these. > > The reference to BDECFLAGS actually isn't true - there is no such > variable. There is a *commented out* version which I had planned to > email you about at some point. The whole file src/share/examples/etc consists of commented-out examples and comments about the examples, with most of its value in the latter. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121130121105.W1707>