Date: Wed, 23 May 2018 11:29:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 205930] clang(1) doesn't document all flags and options Message-ID: <bug-205930-227-RUu1Ten4D9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205930-227@https.bugs.freebsd.org/bugzilla/> References: <bug-205930-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205930 Eitan Adler <eadler@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Works As Intended Status|New |Closed --- Comment #3 from Eitan Adler <eadler@FreeBSD.org> --- You're absolutely correct that clang can do a much better job of documentat= ion its options. That said, since the FreeBSD project uses clang as a pure third party compiler, and isn't in the business of writing a compiler, I am closi= ng this bug without action. It isn't exactly "work's as intended" so much as "we're the wrong people to= fix this issue".=20 It can be argued if we should have taken this into account when we made the switch etc. but this bug is the wrong place for that argument. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205930-227-RUu1Ten4D9>