Hi Reid, > > - possible, by <a href="CommandGuide/html/bugpoint.html">bugpoint</a> or > > + possible, by <a href="Bugpoint.html">bugpoint</a> or > > These aren't the same document. If the bugpoint.html document isn't > there its an artifact of not generating the HTML version from the POD > version. This isn't a huge deal for the link, but do we have a larger > issue generating the command pages?
I first changed this mistakenly, because I hadn't generated the html files, but when I realized it was a mistake it struck me that it was better this way, so I left it rather than changing it back. > > - <li><a href="#checkpoint">Check Points</a></li> > > Can you delete the CheckPoints section too? Its going away soon, when > PR1289 is closed. There is no checkpoints section, there is only "Data Layout". However "Data Layout" talks only of checkpoints. Would you like me to delete it? <div class="doc_subsection"> <a name="datalayout">Data Layout</a> </div> <div class="doc_text"> <p>At the top level, the keyword <tt>checkpoint</tt> may be used to force the assembler to check point the types and values it has defined so far. Any unresolved types or references will generate error messages. This is useful as an assertion point or for debugging.</p> </div> > > - <tr><td><tt>void</tt></td><td>No value</td></tr> > > + <tr><td><tt><a name="t_void">void</a></tt></td><td>No > > value</td></tr> > > <tr><td><tt>i8</tt></td><td>8-bit value</td></tr> > > <tr><td><tt>i32</tt></td><td>32-bit value</td></tr> > > <tr><td><tt>float</tt></td><td>32-bit floating point > > value</td></tr> > > Why not put in links for the other types? Because they have their own sections with an anchor, eg t_integer refers to the section on integers. Void is the only type that doesn't have its own section. Probably it should get one. Ciao, Duncan. _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
