Date: Fri, 30 Nov 2012 09:12:11 +0000 From: David Chisnall <theraven@FreeBSD.org> 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: <4DDE660C-B809-47A5-AEBD-026FAAE8DB8B@FreeBSD.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 30 Nov 2012, at 00:15, Eitan Adler wrote: > Every time I talk to the clang folk about flags they point me to gcc > documentation. No we don't. We point you at the gcc documentation and at the clang manual. Clang aims to support all of the gcc flags, and provides some extra ones as documented here: http://clang.llvm.org/docs/UsersManual.html If you are interested in writing a full manual for clang including the gcc options, then that would almost certainly be appreciated. Most of this can be automatically generated. The best thing to do would be to write a tablegen back end that could emit mandoc from the existing options descriptions. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDE660C-B809-47A5-AEBD-026FAAE8DB8B>