From owner-svn-src-all@FreeBSD.ORG Fri Nov 30 09:12:25 2012 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C3BE15C; Fri, 30 Nov 2012 09:12:25 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id E28B48FC0C; Fri, 30 Nov 2012 09:12:23 +0000 (UTC) Received: from [192.168.0.2] (cpc39-cmbg15-2-0-cust69.5-4.cable.virginmedia.com [81.101.138.70]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id qAU9CFgl019701 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 30 Nov 2012 09:12:16 GMT (envelope-from theraven@FreeBSD.org) Subject: Re: svn commit: r243670 - head/share/man/man5 Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: David Chisnall In-Reply-To: Date: Fri, 30 Nov 2012 09:12:11 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4DDE660C-B809-47A5-AEBD-026FAAE8DB8B@FreeBSD.org> References: <201211291251.qATCpA7w078277@svn.freebsd.org> <20121130110154.E1441@besplex.bde.org> To: Eitan Adler X-Mailer: Apple Mail (2.1278) Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Bruce Evans X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Nov 2012 09:12:25 -0000 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=