[cfe-commits] r42678 - in /cfe/trunk/www: content.css features.html index.html
Chris Lattner
sabre at nondot.org
Fri Oct 5 22:09:05 PDT 2007
Author: lattner
Date: Sat Oct 6 00:09:04 2007
New Revision: 42678
URL: http://llvm.org/viewvc/llvm-project?rev=42678&view=rev
Log:
minor edits
Modified:
cfe/trunk/www/content.css
cfe/trunk/www/features.html
cfe/trunk/www/index.html
Modified: cfe/trunk/www/content.css
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/content.css?rev=42678&r1=42677&r2=42678&view=diff
==============================================================================
--- cfe/trunk/www/content.css (original)
+++ cfe/trunk/www/content.css Sat Oct 6 00:09:04 2007
@@ -9,7 +9,7 @@
padding:0px;
}
p {
- margin-top:0;
+ margin-top:em;
margin-bottom:0;
}
Modified: cfe/trunk/www/features.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/features.html?rev=42678&r1=42677&r2=42678&view=diff
==============================================================================
--- cfe/trunk/www/features.html (original)
+++ cfe/trunk/www/features.html Sat Oct 6 00:09:04 2007
@@ -88,7 +88,7 @@
These are SPEC2006 benchmarks using Distcc.</div>
</div>
-<h2>More Expressive Diagnostics</h2>
+<h2><a name="expressivediags">Expressive Diagnostics</a></h2>
The design of the Clang driver (one of the LLVM front_end libraries) provies more detailed diagnostic information.<br>
<div class="img_container">
<div class="img_title">Clang vs GCC:</div>
Modified: cfe/trunk/www/index.html
URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/index.html?rev=42678&r1=42677&r2=42678&view=diff
==============================================================================
--- cfe/trunk/www/index.html (original)
+++ cfe/trunk/www/index.html Sat Oct 6 00:09:04 2007
@@ -1,49 +1,49 @@
-<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
- <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- <title>Clang c-lang parser for LLVM</title>
- <link type="text/css" rel="stylesheet" href="menu.css" />
- <link type="text/css" rel="stylesheet" href="content.css" />
-</head>
-<body>
- <!--#include virtual="menu.html.incl"-->
- <div id="content">
- <h1>Clang: a C language front-end for LLVM</h1>
- <h2>About</h2>
- <p>The goal of the Clang project is to create a new <a href="http://llvm.org/svn/llvm-project/cfe/trunk/LICENSE.TXT">BSD Licensed</a> C, C++, & ObjC front-end for the <a href="http://www.llvm.org/">LLVM</a> compiler.
- <br><br>
- <p>In the context of this website, the term Clang actually refers to two things:
- <p>1) A "code name" for the LLVM compiler front-end.
- <p>2) A specific library in the LLVM front-end -- in particular the "driver" that makes all the other libraries work together.
- <br><br>
- <p>The developers of Clang include contributers from Apple and numerous other volunteers.
- <h2>Why?</h2>
- <p>The development of a new front-end was started out of a need -- a need for a compiler that allows better diagnostics, better integration with IDEs, a license that is compatible with commercial products, and a compiler that is easier to develop and maintain. All of these were motiviations for starting work on a new C/C++/ObjC front-end that could meet these needs.
- <p>An excellent introduction to Clang can be found in the following video lectures:
- <ul>
- <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>
- <li><a href="clang_video-07-25-2007.html">Features and Performance of Clang</a>
- </ul>
- <h2>Features/Goals</h2>
- Some of the goals for the project include the following:
- <ul>
- <li>Unified parser for C-based languages
- <li>Language conformance with C99, ObjC, C++
- <li>Real-world, production quality compiler
- <li>GCC compatibility
- <li>Library based architecture with finely crafted C++ API's
- <li>High performance
- <li>Better integration with IDEs
- <li>Expressive diagnostics
- <li>BSD License
- </ul>
- Of course this is only a rough outline of the goals and features of Clang. To get a true sense of what the new LLVM front-end is all about, as well as why you might want to considering using it, see the <a href="features.html">Features</a> section.
- <h2>Try Clang</h2>
- If you are a compiler developer and want to try out Clang, then build instructions are available on the <a href="get_involved.html#build">Get Involved</a> page.
- <h2>Get Involved</h2>
- If you are interested in working on Clang, then check out the <a href="get_involved.html">Get Involved</a> section.
- </div>
-</body>
+<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ -->
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+ <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ <title>Clang c-lang parser for LLVM</title>
+ <link type="text/css" rel="stylesheet" href="menu.css" />
+ <link type="text/css" rel="stylesheet" href="content.css" />
+</head>
+<body>
+ <!--#include virtual="menu.html.incl"-->
+ <div id="content">
+ <h1>Clang: a C language front-end for LLVM</h1>
+ <h2>About</h2>
+ <p>The goal of the Clang project is to create a new <a href="http://llvm.org/svn/llvm-project/cfe/trunk/LICENSE.TXT">BSD Licensed</a> C, C++, & ObjC front-end for the <a href="http://www.llvm.org/">LLVM</a> compiler.
+ <br><br>
+ <p>In the context of this website, the term Clang actually refers to two things:
+ <p>1) A "code name" for the LLVM compiler front-end.
+ <p>2) A specific library in the LLVM front-end -- in particular the "driver" that makes all the other libraries work together.
+ <br><br>
+ <p>The developers of Clang include contributers from Apple and numerous other volunteers.
+ <h2>Why?</h2>
+ <p>The development of a new front-end was started out of a need -- a need for a compiler that allows better diagnostics, better integration with IDEs, a license that is compatible with commercial products, and a compiler that is easier to develop and maintain. All of these were motivations for starting work on a new C/C++/ObjC front-end that could meet these needs.
+ <p>An excellent introduction to Clang can be found in the following video lectures:
+ <ul>
+ <li><a href="clang_video-05-25-2007.html">Clang Introduction</a>
+ <li><a href="clang_video-07-25-2007.html">Features and Performance of Clang</a>
+ </ul>
+ <h2>Features/Goals</h2>
+ Some of the goals for the project include the following:
+ <ul>
+ <li>Real-world, production quality compiler.</li>
+ <li>A single unified parser for C/ObjC/C++</li>
+ <li>Language conformance with C, ObjC, C++ (including variants, like C90, C99, etc)</li>
+ <li>GCC compatibility (supports GCC extensions, but allow them to be disabled)</li>
+ <li>Library based architecture with finely crafted C++ API's</li>
+ <li>High performance</li>
+ <li>Design for integration with IDEs as well as code generation with <a href="http://llvm.org">LLVM</a>.</li>
+ <li><a href="features.html#expressivediags">Expressive diagnostics</a></li>
+ <li>BSD License</li>
+ </ul>
+ Of course this is only a rough outline of the goals and features of Clang. To get a true sense of what the new LLVM front-end is all about, as well as why you might want to considering using it, see the <a href="features.html">Features</a> section.
+ <h2>Try Clang</h2>
+ If you are a compiler developer and want to try out Clang, then build instructions are available on the <a href="get_involved.html#build">Get Involved</a> page.
+ <h2>Get Involved</h2>
+ If you are interested in working on Clang, then check out the <a href="get_involved.html">Get Involved</a> section.
+ </div>
+</body>
</html>
\ No newline at end of file
More information about the cfe-commits
mailing list