<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 18, 2014 at 5:56 PM, Adrian Prantl <span dir="ltr"><<a href="mailto:aprantl@apple.com" target="_blank">aprantl@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
> On Jun 15, 2014, at 1:07 PM, Alp Toker <<a href="mailto:alp@nuanti.com">alp@nuanti.com</a>> wrote:<br>
><br>
><br>
> On 14/06/2014 00:12, Adrian Prantl wrote:<br>
>> Author: adrian<br>
>> Date: Fri Jun 13 16:12:31 2014<br>
>> New Revision: 210936<br>
>><br>
>> URL: <a href="http://llvm.org/viewvc/llvm-project?rev=210936&view=rev" target="_blank">http://llvm.org/viewvc/llvm-project?rev=210936&view=rev</a><br>
>> Log:<br>
>> Copy the documentation of -fstandalone-debug from the man page to the user<br>
>> manual.<br>
><br>
> Hi Adrian,<br>
><br>
> It bothers me that we now have two copies of this documentation in-tree.<br>
><br>
> There are readily available tools to generate man pages from rst files. The cost of hooking a doc tool up to the build system is certainly lower than having skilled compiler engineers maintain two divergent copies of the documentation (history shows we have a hard enough time maintaining a single set of quality docs, let alone two).<br>
><br>
> Do you have a timeline to remove one of the duplicate copies?<br>
<br>
</div>Hi Alp,<br>
<br>
I think this is a reasonable suggestion, but after comparing the user manual and the man page, I’m unsure what the best way to proceed here is. There obviously is some overlap between user manual and man page, and we might be able to extract a common core that is shared between user manual and man page and automatically inserted into both at documentation build time. But the man page can also be seen as a condensed version of the user manual</blockquote>
<div><br></div><div>Users expect a manpage to be an authoritative references for the commandline options of a program. It is not a "condensed" version of anything. It is the reference documentation for the option.</div>
<div><br></div><div>That being said, clang's manpage is pretty sad and we currently do not maintain it aiming for the goal I set out in the previous paragraph.</div><div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
that only briefly lists all the options and everything that is necessary to invoke the various tools on the command line, and form that point of view, it is not clear whether it is even desirable to unify those two texts.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- adrian<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> Alp.<br>
><br>
><br>
><br>
>><br>
>> rdar://problem/17307006<br>
>><br>
>> Modified:<br>
>> cfe/trunk/docs/UsersManual.rst<br>
>><br>
>> Modified: cfe/trunk/docs/UsersManual.rst<br>
>> URL: <a href="http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/UsersManual.rst?rev=210936&r1=210935&r2=210936&view=diff" target="_blank">http://llvm.org/viewvc/llvm-project/cfe/trunk/docs/UsersManual.rst?rev=210936&r1=210935&r2=210936&view=diff</a><br>
>> ==============================================================================<br>
>> --- cfe/trunk/docs/UsersManual.rst (original)<br>
>> +++ cfe/trunk/docs/UsersManual.rst Fri Jun 13 16:12:31 2014<br>
>> @@ -1298,6 +1298,22 @@ below. If multiple flags are present, th<br>
>> doesn't contain any other data (e.g. description of local variables or<br>
>> function parameters).<br>
>> +.. option:: -fstandalone-debug -fno-standalone-debug<br>
>> +<br>
>> + Clang supports a number of optimizations to reduce the size of debug<br>
>> + information in the binary. They work based on the assumption that<br>
>> + the debug type information can be spread out over multiple<br>
>> + compilation units. For instance, Clang will not emit type<br>
>> + definitions for types that are not needed by a module and could be<br>
>> + replaced with a forward declaration. Further, Clang will only emit<br>
>> + type info for a dynamic C++ class in the module that contains the<br>
>> + vtable for the class.<br>
>> +<br>
>> + The ``-fstandalone-debug`` option turns off these optimizations.<br>
>> + This is useful when working with 3rd-party libraries that don't come<br>
>> + with debug information. Note that Clang will never emit type<br>
>> + information for types that are not referenced at all by the program.<br>
>> +<br>
>> .. option:: -g<br>
>> Generate complete debug info.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> cfe-commits mailing list<br>
>> <a href="mailto:cfe-commits@cs.uiuc.edu">cfe-commits@cs.uiuc.edu</a><br>
>> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits</a><br>
><br>
> --<br>
> <a href="http://www.nuanti.com" target="_blank">http://www.nuanti.com</a><br>
> the browser experts<br>
<br>
<br>
_______________________________________________<br>
cfe-commits mailing list<br>
<a href="mailto:cfe-commits@cs.uiuc.edu">cfe-commits@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits</a><br>
</div></div></blockquote></div><br></div></div>