6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-06-26 10:29:57 +00:00
Code Issues Projects Releases Wiki Activity

docs/*.html: Make W3C HTML 4.01 Strict more compliant.

Browse Source 
FIXME: The logo handling in ReleaseNotes.html

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129208 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
NAKAMURA Takumi 2011-04-09 09:51:57 +00:00
parent 18a2e50a9b
commit 4d6deb099e
15 changed files with 38 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/AliasAnalysis.html
View File

@ -567,7 +567,7 @@ which are intended to allow a pass to keep an AliasAnalysis consistent,
however there's no way for a pass to declare in its
<tt>getAnalysisUsage</tt> that it does so. Some passes attempt to use
<tt>AU.addPreserved&lt;AliasAnalysis&gt;</tt>, however this doesn't
actually have any effect.</tt>
actually have any effect.</p>
<p><tt>AliasAnalysisCounter</tt> (<tt>-count-aa</tt>) and <tt>AliasDebugger</tt>
(<tt>-debug-aa</tt>) are implemented as <tt>ModulePass</tt> classes, so if your

2
docs/BitCodeFormat.html
View File

@ -980,7 +980,7 @@ index in the table of
<a href="#MODULE_CODE_GCNAME">MODULE_CODE_GCNAME</a> entries.</li>
<li><i>unnamed_addr</i>: If present and non-zero, indicates that the function
has <tt>unnamed_addr<tt></li>
has <tt>unnamed_addr</tt></li>
</ul>
</div>

2
docs/CMake.html
View File

@ -342,7 +342,7 @@
<dt><b>LLVM_LIT_TOOLS_DIR</b>:STRING</dt>
<dd>The path to GnuWin32 tools for tests. Valid on Windows host.
Defaults to "", then Lit seeks tools according to %PATH%.
Lit can find tools(eg. grep, sort, &c) on LLVM_LIT_TOOLS_DIR at first,
Lit can find tools(eg. grep, sort, &amp;c) on LLVM_LIT_TOOLS_DIR at first,
without specifying GnuWin32 to %PATH%.</dd>
<dt><b>LLVM_ENABLE_FFI</b>:BOOL</dt>

4
docs/GarbageCollection.html
View File

@ -151,14 +151,14 @@ collector models. For instance, the intrinsics permit:</p>
support a broad class of garbage collected languages including Scheme, ML, Java,
C#, Perl, Python, Lua, Ruby, other scripting languages, and more.</p>
<p>However, LLVM does not itself provide a garbage collector&#151;this should
<p>However, LLVM does not itself provide a garbage collector&mdash;this should
be part of your language's runtime library. LLVM provides a framework for
compile time <a href="#plugin">code generation plugins</a>. The role of these
plugins is to generate code and data structures which conforms to the <em>binary
interface</em> specified by the <em>runtime library</em>. This is similar to the
relationship between LLVM and DWARF debugging info, for example. The
difference primarily lies in the lack of an established standard in the domain
of garbage collection&#151;thus the plugins.</p>
of garbage collection&mdash;thus the plugins.</p>
<p>The aspects of the binary interface with which LLVM's GC support is
concerned are:</p>

12
docs/GettingStarted.html
View File

@ -116,7 +116,7 @@ and performance.
<li>Read the documentation.</li>
<li>Remember that you were warned twice about reading the documentation.</li>
<li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
(see <a href="#installcf">Install the GCC Front End</a> for details):</li>
(see <a href="#installcf">Install the GCC Front End</a> for details):
<ol>
<li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
<li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
@ -344,9 +344,9 @@ up</a></li>
ActivePerl, as these have Windows-specifics that will cause the
build to fail.</a></li>
<li><a name="pf_11">To use LLVM modules on Win32-based system,
you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</li>
you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
<li><a name="pf_12">To compile SPU backend, you need to add
<tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</li>
<tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
</ol>
</div>
@ -801,11 +801,11 @@ instructions</a> to successfully get and build the LLVM GCC front-end.</p>
sync automatically with each Subversion commit and contain all necessary
git-svn marks (so, you can recreate git-svn metadata locally). Note that right
now mirrors reflect only <tt>trunk</tt> for each project. You can do the
read-only GIT clone of LLVM via:
read-only GIT clone of LLVM via:</p>
<pre>
% git clone http://llvm.org/git/llvm.git
</pre>
</p>
</div>
@ -1238,7 +1238,7 @@ $ ./hello.bc
<p>
This allows you to execute LLVM bitcode files directly. On Debian, you
can also use this command instead of the 'echo' command above:</p>
can also use this command instead of the 'echo' command above:
</p>
<div class="doc_code">

5
docs/GettingStartedVS.html
View File

@ -213,14 +213,15 @@
<p>Note that quite a few of these test will fail.</p>
</li>
<li>A specific test or test directory can be run with:</li>
<li>A specific test or test directory can be run with:
<div class="doc_code">
<pre>
% llvm-lit test/path/to/test
</pre>
</div>
</li>
</ul>
</ol>
</div>

13
docs/HowToReleaseLLVM.html
View File

@ -82,12 +82,13 @@
<div class="doc_text">
<ol>
<li><a href="#release-admin">Release Administrative Tasks</a></li>
<li><a href="#release-admin">Release Administrative Tasks</a>
<ol>
<li><a href="#branch">Create Release Branch</a></li>
<li><a href="#verchanges">Update Version Numbers</a></li>
</ol>
<li><a href="#release-build">Building the Release</a></li>
</li>
<li><a href="#release-build">Building the Release</a>
<ol>
<li><a href="#dist">Build the LLVM Source Distributions</a></li>
<li><a href="#build">Build LLVM</a></li>
@ -95,18 +96,19 @@
<li><a href="#clangbin">Build the Clang Binary Distribution</a></li>
<li><a href="#target-build">Target Specific Build Details</a></li>
</ol>
<li><a href="#release-qualify">Release Qualification Criteria</a></li>
</li>
<li><a href="#release-qualify">Release Qualification Criteria</a>
<ol>
<li><a href="#llvm-qualify">Qualify LLVM</a></li>
<li><a href="#llvmgcc-qualify">Qualify LLVM-GCC</a></li>
<li><a href="#clang-qualify">Qualify Clang</a></li>
<li><a href="#targets">Specific Target Qualification Details</a></li>
</ol>
</li>
<li><a href="#commTest">Community Testing</a></li>
<li><a href="#release-patch">Release Patch Rules</a></li>
<li><a href="#release-final">Release final tasks</a></li>
<li><a href="#release-final">Release final tasks</a>
<ol>
<li><a href="#updocs">Update Documentation</a></li>
<li><a href="#tag">Tag the LLVM Final Release</a></li>
@ -114,6 +116,7 @@
<li><a href="#webupdates">Update the LLVM Website</a></li>
<li><a href="#announce">Announce the Release</a></li>
</ol>
</li>
</ol>
</div>

3
docs/ReleaseNotes.html
View File

@ -3,7 +3,6 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta encoding="utf8">
<link rel="stylesheet" href="llvm.css" type="text/css">
<title>LLVM 2.9 Release Notes</title>
</head>
@ -119,8 +118,6 @@ look at the <a href="http://clang.llvm.org/compatibility.html">language
compatibility</a> guide to make sure this is not intentional or a known issue.
</p>
<ul>
</ul>
</div>
<!--=========================================================================-->

2
docs/SourceLevelDebugging.html
View File

@ -804,7 +804,7 @@ DW_TAG_return_variable = 258
</pre>
<p>This intrinsic provides information about a local element (ex. variable.) The
first argument is metadata holding alloca for the variable.</tt>. The
first argument is metadata holding alloca for the variable. The
second argument is metadata containing description of the variable. </p>
</div>

1
docs/TestingGuide.html
View File

@ -295,6 +295,7 @@ that subdirectory.</p>
<div class="doc_subsection"><a name="quickdebuginfotests">Debugging Information
tests</a></div>
<!-- _______________________________________________________________________ -->
<div class="doc_text">
<p> To run debugging information tests simply checkout the tests inside
clang/test directory. </p>

16
docs/UsingLibraries.html
View File

@ -26,7 +26,7 @@
<p class="doc_warning">Warning: This document is out of date, for more
information please
see <a href="CommandGuide/html/llvm-config.html">llvm-config</a> or,
if you use CMake, <a href=CMake.html#embedding>the CMake LLVM
if you use CMake, <a href="CMake.html#embedding">the CMake LLVM
guide</a>.</p>
<!-- ======================================================================= -->
@ -191,12 +191,12 @@
<p>This graph shows the dependency of archive libraries on other archive
libraries or objects. Where a library has both archive and object forms, only
the archive form is shown.</p>
<img src="img/libdeps.gif" alt="Library Dependencies"/>
<img src="img/libdeps.gif" alt="Library Dependencies">
<h2>Dependency Relationships Of Object Files</h2>
<p>This graph shows the dependency of object files on archive libraries or
other objects. Where a library has both object and archive forms, only the
dependency to the archive form is shown.</p>
<img src="img/objdeps.gif" alt="Object File Dependencies"/>
<img src="img/objdeps.gif" alt="Object File Dependencies">
<p>The following list shows the dependency relationships between libraries in
textual form. The information is the same as shown on the graphs but arranged
alphabetically.</p>
@ -280,8 +280,8 @@
<li>libLLVMSystem.a</li>
<li>libLLVMbzip2.a</li>
</ul></dd>
<dt><b>libLLVMSystem.a</b></dt><dd><ul>
</ul></dd>
<dt><b>libLLVMSystem.a</b></dt><dd>
</dd>
<dt><b>libLLVMTarget.a</b></dt><dd><ul>
<li>libLLVMCore.a</li>
<li>libLLVMSupport.a</li>
@ -295,8 +295,8 @@
<li>libLLVMTarget.a</li>
<li>libLLVMipa.a</li>
</ul></dd>
<dt><b>libLLVMbzip2.a</b></dt><dd><ul>
</ul></dd>
<dt><b>libLLVMbzip2.a</b></dt><dd>
</dd>
<dt><b>libLLVMipa.a</b></dt><dd><ul>
<li>libLLVMAnalysis.a</li>
<li>libLLVMCore.a</li>
@ -430,7 +430,7 @@
<div class="doc_footer">
<address>
<a href="http://jigsaw.w3.org/css-validator/check/referer"><img
src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"/></a>
src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
<a href="http://validator.w3.org/check/referer"><img
src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
<a href="mailto:rspencer@x10sys.com">Reid Spencer</a>

6
docs/WritingAnLLVMPass.html
View File

@ -185,7 +185,7 @@ source tree in the <tt>lib/Transforms/Hello</tt> directory.</p>
<tt>lib/Transforms/Hello</tt>. Finally, you must set up a build script
(Makefile) that will compile the source code for the new pass. To do this,
copy the following into <tt>Makefile</tt>:</p>
<hr/>
<hr>
<div class="doc_code"><pre>
# Makefile for hello pass
@ -301,7 +301,7 @@ function.</p>
initialization value is not important.</p>
<div class="doc_code"><pre>
static RegisterPass<Hello> X("<i>hello</i>", "<i>Hello World Pass</i>",
static RegisterPass&lt;Hello&gt; X("<i>hello</i>", "<i>Hello World Pass</i>",
false /* Only looks at CFG */,
false /* Analysis Pass */);
} <i>// end of anonymous namespace</i>
@ -337,7 +337,7 @@ is supplied as fourth argument. </p>
};
char Hello::ID = 0;
static RegisterPass<Hello> X("hello", "Hello World Pass", false, false);
static RegisterPass&lt;Hello&gt; X("hello", "Hello World Pass", false, false);
}
</pre></div>

2
docs/tutorial/LangImpl4.html
View File

@ -1078,7 +1078,7 @@ int main() {
// Create the JIT. This takes ownership of the module.
std::string ErrStr;
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&amp;ErrStr).create();
if (!TheExecutionEngine) {
fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
exit(1);

2
docs/tutorial/LangImpl5.html
View File

@ -1721,7 +1721,7 @@ int main() {
// Create the JIT. This takes ownership of the module.
std::string ErrStr;
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&amp;ErrStr).create();
if (!TheExecutionEngine) {
fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
exit(1);

2
docs/tutorial/LangImpl6.html
View File

@ -1758,7 +1758,7 @@ int main() {
// Create the JIT. This takes ownership of the module.
std::string ErrStr;
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&ErrStr).create();
TheExecutionEngine = EngineBuilder(TheModule).setErrorStr(&amp;ErrStr).create();
if (!TheExecutionEngine) {
fprintf(stderr, "Could not create ExecutionEngine: %s\n", ErrStr.c_str());
exit(1);