1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <title>LLVM Developer Policy</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
11 <div class="doc_title">LLVM Developer Policy</div>
13 <li><a href="#introduction">Introduction</a></li>
14 <li><a href="#policies">Developer Policies</a>
16 <li><a href="#informed">Stay Informed</a></li>
17 <li><a href="#patches">Making a Patch</a></li>
18 <li><a href="#reviews">Code Reviews</a></li>
19 <li><a href="#owners">Code Owners</a></li>
20 <li><a href="#testcases">Test Cases</a></li>
21 <li><a href="#quality">Quality</a></li>
22 <li><a href="#commitaccess">Obtaining Commit Access</a></li>
23 <li><a href="#newwork">Making a Major Change</a></li>
24 <li><a href="#incremental">Incremental Development</a></li>
25 <li><a href="#attribution">Attribution of Changes</a></li>
27 <li><a href="#clp">Copyright, License, and Patents</a>
29 <li><a href="#copyright">Copyright</a></li>
30 <li><a href="#license">License</a></li>
31 <li><a href="#patents">Patents</a></li>
32 <li><a href="#devagree">Developer Agreements</a></li>
35 <div class="doc_author">Written by the LLVM Oversight Team</div>
37 <!--=========================================================================-->
38 <div class="doc_section"><a name="introduction">Introduction</a></div>
39 <!--=========================================================================-->
40 <div class="doc_text">
41 <p>This document contains the LLVM Developer Policy which defines the project's
42 policy towards developers and their contributions. The intent of this policy
43 is to eliminate miscommunication, rework, and confusion that might arise from
44 the distributed nature of LLVM's development. By stating the policy in clear
45 terms, we hope each developer can know ahead of time what to expect when
46 making LLVM contributions. This policy covers all llvm.org subprojects,
47 including Clang, LLDB, etc.</p>
48 <p>This policy is also designed to accomplish the following objectives:</p>
51 <li>Attract both users and developers to the LLVM project.</li>
53 <li>Make life as simple and easy for contributors as possible.</li>
55 <li>Keep the top of Subversion trees as stable as possible.</li>
58 <p>This policy is aimed at frequent contributors to LLVM. People interested in
59 contributing one-off patches can do so in an informal way by sending them to
61 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits
62 mailing list</a> and engaging another developer to see it through the
66 <!--=========================================================================-->
67 <div class="doc_section"><a name="policies">Developer Policies</a></div>
68 <!--=========================================================================-->
69 <div class="doc_text">
70 <p>This section contains policies that pertain to frequent LLVM developers. We
71 always welcome <a href="#patches">one-off patches</a> from people who do not
72 routinely contribute to LLVM, but we expect more from frequent contributors
73 to keep the system as efficient as possible for everyone. Frequent LLVM
74 contributors are expected to meet the following requirements in order for
75 LLVM to maintain a high standard of quality.<p>
78 <!-- _______________________________________________________________________ -->
79 <div class="doc_subsection"> <a name="informed">Stay Informed</a> </div>
80 <div class="doc_text">
81 <p>Developers should stay informed by reading at least the "dev" mailing list
82 for the projects you are interested in, such as
83 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a> for
84 LLVM, <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">cfe-dev</a>
86 href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">lldb-dev</a>
87 for LLDB. If you are doing anything more than just casual work on LLVM, it
88 is suggested that you also subscribe to the "commits" mailing list for the
89 subproject you're interested in, such as
90 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>,
91 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits">cfe-commits</a>,
92 or <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits">lldb-commits</a>.
93 Reading the "commits" list and paying attention to changes being made by
94 others is a good way to see what other people are interested in and watching
95 the flow of the project as a whole.</p>
97 <p>We recommend that active developers register an email account with
98 <a href="http://llvm.org/bugs/">LLVM Bugzilla</a> and preferably subscribe to
99 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs">llvm-bugs</a>
100 email list to keep track of bugs and enhancements occurring in LLVM. We
101 really appreciate people who are proactive at catching incoming bugs in their
102 components and dealing with them promptly.</p>
105 <!-- _______________________________________________________________________ -->
106 <div class="doc_subsection"> <a name="patches">Making a Patch</a></div>
108 <div class="doc_text">
109 <p>When making a patch for review, the goal is to make it as easy for the
110 reviewer to read it as possible. As such, we recommend that you:</p>
113 <li>Make your patch against the Subversion trunk, not a branch, and not an old
114 version of LLVM. This makes it easy to apply the patch. For information
115 on how to check out SVN trunk, please see the <a
116 href="GettingStarted.html#checkout">Getting Started Guide</a>.</li>
118 <li>Similarly, patches should be submitted soon after they are generated. Old
119 patches may not apply correctly if the underlying code changes between the
120 time the patch was created and the time it is applied.</li>
122 <li>Patches should be made with <tt>svn diff</tt>, or similar. If you use
123 a different tool, make sure it uses the <tt>diff -u</tt> format and
124 that it doesn't contain clutter which makes it hard to read.</li>
126 <li>If you are modifying generated files, such as the top-level
127 <tt>configure</tt> script, please separate out those changes into
128 a separate patch from the rest of your changes.</li>
131 <p>When sending a patch to a mailing list, it is a good idea to send it as an
132 <em>attachment</em> to the message, not embedded into the text of the
133 message. This ensures that your mailer will not mangle the patch when it
134 sends it (e.g. by making whitespace changes or by wrapping lines).</p>
136 <p><em>For Thunderbird users:</em> Before submitting a patch, please open
137 <em>Preferences → Advanced → General → Config Editor</em>,
138 find the key <tt>mail.content_disposition_type</tt>, and set its value to
139 <tt>1</tt>. Without this setting, Thunderbird sends your attachment using
140 <tt>Content-Disposition: inline</tt> rather than <tt>Content-Disposition:
141 attachment</tt>. Apple Mail gamely displays such a file inline, making it
142 difficult to work with for reviewers using that program.</p>
145 <!-- _______________________________________________________________________ -->
146 <div class="doc_subsection"> <a name="reviews">Code Reviews</a></div>
147 <div class="doc_text">
148 <p>LLVM has a code review policy. Code review is one way to increase the quality
149 of software. We generally follow these policies:</p>
152 <li>All developers are required to have significant changes reviewed before
153 they are committed to the repository.</li>
155 <li>Code reviews are conducted by email, usually on the llvm-commits
158 <li>Code can be reviewed either before it is committed or after. We expect
159 major changes to be reviewed before being committed, but smaller changes
160 (or changes where the developer owns the component) can be reviewed after
163 <li>The developer responsible for a code change is also responsible for making
164 all necessary review-related changes.</li>
166 <li>Code review can be an iterative process, which continues until the patch
167 is ready to be committed.</li>
170 <p>Developers should participate in code reviews as both reviewers and
171 reviewees. If someone is kind enough to review your code, you should return
172 the favor for someone else. Note that anyone is welcome to review and give
173 feedback on a patch, but only people with Subversion write access can approve
177 <!-- _______________________________________________________________________ -->
178 <div class="doc_subsection"> <a name="owners">Code Owners</a></div>
179 <div class="doc_text">
181 <p>The LLVM Project relies on two features of its process to maintain rapid
182 development in addition to the high quality of its source base: the
183 combination of code review plus post-commit review for trusted maintainers.
184 Having both is a great way for the project to take advantage of the fact that
185 most people do the right thing most of the time, and only commit patches
186 without pre-commit review when they are confident they are right.</p>
188 <p>The trick to this is that the project has to guarantee that all patches that
189 are committed are reviewed after they go in: you don't want everyone to
190 assume someone else will review it, allowing the patch to go unreviewed. To
191 solve this problem, we have a notion of an 'owner' for a piece of the code.
192 The sole responsibility of a code owner is to ensure that a commit to their
193 area of the code is appropriately reviewed, either by themself or by someone
194 else. The current code owners are:</p>
197 <li><b>Evan Cheng</b>: Code generator and all targets.</li>
199 <li><b>Doug Gregor</b>: Clang Basic, Lex, Parse, and Sema Libraries.</li>
201 <li><b>Anton Korobeynikov</b>: Exception handling, debug information, and
202 Windows codegen.</li>
204 <li><b>Ted Kremenek</b>: Clang Static Analyzer.</li>
206 <li><b>Chris Lattner</b>: Everything not covered by someone else.</li>
208 <li><b>Duncan Sands</b>: llvm-gcc 4.2.</li>
211 <p>Note that code ownership is completely different than reviewers: anyone can
212 review a piece of code, and we welcome code review from anyone who is
213 interested. Code owners are the "last line of defense" to guarantee that all
214 patches that are committed are actually reviewed.</p>
216 <p>Being a code owner is a somewhat unglamorous position, but it is incredibly
217 important for the ongoing success of the project. Because people get busy,
218 interests change, and unexpected things happen, code ownership is purely
219 opt-in, and anyone can choose to resign their "title" at any time. For now,
220 we do not have an official policy on how one gets elected to be a code
224 <!-- _______________________________________________________________________ -->
225 <div class="doc_subsection"> <a name="testcases">Test Cases</a></div>
226 <div class="doc_text">
227 <p>Developers are required to create test cases for any bugs fixed and any new
228 features added. Some tips for getting your testcase approved:</p>
231 <li>All feature and regression test cases are added to the
232 <tt>llvm/test</tt> directory. The appropriate sub-directory should be
233 selected (see the <a href="TestingGuide.html">Testing Guide</a> for
236 <li>Test cases should be written in <a href="LangRef.html">LLVM assembly
237 language</a> unless the feature or regression being tested requires
238 another language (e.g. the bug being fixed or feature being implemented is
239 in the llvm-gcc C++ front-end, in which case it must be written in
242 <li>Test cases, especially for regressions, should be reduced as much as
243 possible, by <a href="Bugpoint.html">bugpoint</a> or manually. It is
244 unacceptable to place an entire failing program into <tt>llvm/test</tt> as
245 this creates a <i>time-to-test</i> burden on all developers. Please keep
249 <p>Note that llvm/test and clang/test are designed for regression and small
250 feature tests only. More extensive test cases (e.g., entire applications,
252 should be added to the <tt>llvm-test</tt> test suite. The llvm-test suite is
253 for coverage (correctness, performance, etc) testing, not feature or
254 regression testing.</p>
257 <!-- _______________________________________________________________________ -->
258 <div class="doc_subsection"> <a name="quality">Quality</a></div>
259 <div class="doc_text">
260 <p>The minimum quality standards that any change must satisfy before being
261 committed to the main development branch are:</p>
264 <li>Code must adhere to the <a href="CodingStandards.html">LLVM Coding
267 <li>Code must compile cleanly (no errors, no warnings) on at least one
270 <li>Bug fixes and new features should <a href="#testcases">include a
271 testcase</a> so we know if the fix/feature ever regresses in the
274 <li>Code must pass the <tt>llvm/test</tt> test suite.</li>
276 <li>The code must not cause regressions on a reasonable subset of llvm-test,
277 where "reasonable" depends on the contributor's judgement and the scope of
278 the change (more invasive changes require more testing). A reasonable
279 subset might be something like
280 "<tt>llvm-test/MultiSource/Benchmarks</tt>".</li>
283 <p>Additionally, the committer is responsible for addressing any problems found
284 in the future that the change is responsible for. For example:</p>
287 <li>The code should compile cleanly on all supported platforms.</li>
289 <li>The changes should not cause any correctness regressions in the
290 <tt>llvm-test</tt> suite and must not cause any major performance
293 <li>The change set should not cause performance or correctness regressions for
296 <li>The changes should not cause performance or correctness regressions in
297 code compiled by LLVM on all applicable targets.</li>
299 <li>You are expected to address any <a href="http://llvm.org/bugs/">bugzilla
300 bugs</a> that result from your change.</li>
303 <p>We prefer for this to be handled before submission but understand that it
304 isn't possible to test all of this for every submission. Our build bots and
305 nightly testing infrastructure normally finds these problems. A good rule of
306 thumb is to check the nightly testers for regressions the day after your
307 change. Build bots will directly email you if a group of commits that
308 included yours caused a failure. You are expected to check the build bot
309 messages to see if they are your fault and, if so, fix the breakage.</p>
311 <p>Commits that violate these quality standards (e.g. are very broken) may be
312 reverted. This is necessary when the change blocks other developers from
313 making progress. The developer is welcome to re-commit the change after the
314 problem has been fixed.</p>
317 <!-- _______________________________________________________________________ -->
318 <div class="doc_subsection">
319 <a name="commitaccess">Obtaining Commit Access</a></div>
320 <div class="doc_text">
322 <p>We grant commit access to contributors with a track record of submitting high
323 quality patches. If you would like commit access, please send an email to
324 <a href="mailto:sabre@nondot.org">Chris</a> with the following
328 <li>The user name you want to commit with, e.g. "hacker".</li>
330 <li>The full name and email address you want message to llvm-commits to come
331 from, e.g. "J. Random Hacker <hacker@yoyodyne.com>".</li>
333 <li>A "password hash" of the password you want to use, e.g. "2ACR96qjUqsyM".
334 Note that you don't ever tell us what your password is, you just give it
335 to us in an encrypted form. To get this, run "htpasswd" (a utility that
336 comes with apache) in crypt mode (often enabled with "-d"), or find a web
337 page that will do it for you.</li>
340 <p>Once you've been granted commit access, you should be able to check out an
341 LLVM tree with an SVN URL of "https://username@llvm.org/..." instead of the
342 normal anonymous URL of "http://llvm.org/...". The first time you commit
343 you'll have to type in your password. Note that you may get a warning from
344 SVN about an untrusted key, you can ignore this. To verify that your commit
345 access works, please do a test commit (e.g. change a comment or add a blank
346 line). Your first commit to a repository may require the autogenerated email
347 to be approved by a mailing list. This is normal, and will be done when
348 the mailing list owner has time.</p>
350 <p>If you have recently been granted commit access, these policies apply:</p>
353 <li>You are granted <i>commit-after-approval</i> to all parts of LLVM. To get
354 approval, submit a <a href="#patches">patch</a> to
355 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>.
356 When approved you may commit it yourself.</li>
358 <li>You are allowed to commit patches without approval which you think are
359 obvious. This is clearly a subjective decision — we simply expect
360 you to use good judgement. Examples include: fixing build breakage,
361 reverting obviously broken patches, documentation/comment changes, any
362 other minor changes.</li>
364 <li>You are allowed to commit patches without approval to those portions of
365 LLVM that you have contributed or maintain (i.e., have been assigned
366 responsibility for), with the proviso that such commits must not break the
367 build. This is a "trust but verify" policy and commits of this nature are
368 reviewed after they are committed.</li>
370 <li>Multiple violations of these policies or a single egregious violation may
371 cause commit access to be revoked.</li>
374 <p>In any case, your changes are still subject to <a href="#reviews">code
375 review</a> (either before or after they are committed, depending on the
376 nature of the change). You are encouraged to review other peoples' patches
377 as well, but you aren't required to.</p>
380 <!-- _______________________________________________________________________ -->
381 <div class="doc_subsection"> <a name="newwork">Making a Major Change</a></div>
382 <div class="doc_text">
383 <p>When a developer begins a major new project with the aim of contributing it
384 back to LLVM, s/he should inform the community with an email to
385 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a>
386 email list, to the extent possible. The reason for this is to:
389 <li>keep the community informed about future changes to LLVM, </li>
391 <li>avoid duplication of effort by preventing multiple parties working on the
392 same thing and not knowing about it, and</li>
394 <li>ensure that any technical issues around the proposed work are discussed
395 and resolved before any significant work is done.</li>
398 <p>The design of LLVM is carefully controlled to ensure that all the pieces fit
399 together well and are as consistent as possible. If you plan to make a major
400 change to the way LLVM works or want to add a major new extension, it is a
401 good idea to get consensus with the development community before you start
404 <p>Once the design of the new feature is finalized, the work itself should be
405 done as a series of <a href="#incremental">incremental changes</a>, not as a
406 long-term development branch.</p>
409 <!-- _______________________________________________________________________ -->
410 <div class="doc_subsection"> <a name="incremental">Incremental Development</a>
412 <div class="doc_text">
413 <p>In the LLVM project, we do all significant changes as a series of incremental
414 patches. We have a strong dislike for huge changes or long-term development
415 branches. Long-term development branches have a number of drawbacks:</p>
418 <li>Branches must have mainline merged into them periodically. If the branch
419 development and mainline development occur in the same pieces of code,
420 resolving merge conflicts can take a lot of time.</li>
422 <li>Other people in the community tend to ignore work on branches.</li>
424 <li>Huge changes (produced when a branch is merged back onto mainline) are
425 extremely difficult to <a href="#reviews">code review</a>.</li>
427 <li>Branches are not routinely tested by our nightly tester
430 <li>Changes developed as monolithic large changes often don't work until the
431 entire set of changes is done. Breaking it down into a set of smaller
432 changes increases the odds that any of the work will be committed to the
433 main repository.</li>
436 <p>To address these problems, LLVM uses an incremental development style and we
437 require contributors to follow this practice when making a large/invasive
438 change. Some tips:</p>
441 <li>Large/invasive changes usually have a number of secondary changes that are
442 required before the big change can be made (e.g. API cleanup, etc). These
443 sorts of changes can often be done before the major change is done,
444 independently of that work.</li>
446 <li>The remaining inter-related work should be decomposed into unrelated sets
447 of changes if possible. Once this is done, define the first increment and
448 get consensus on what the end goal of the change is.</li>
450 <li>Each change in the set can be stand alone (e.g. to fix a bug), or part of
451 a planned series of changes that works towards the development goal.</li>
453 <li>Each change should be kept as small as possible. This simplifies your work
454 (into a logical progression), simplifies code review and reduces the
455 chance that you will get negative feedback on the change. Small increments
456 also facilitate the maintenance of a high quality code base.</li>
458 <li>Often, an independent precursor to a big change is to add a new API and
459 slowly migrate clients to use the new API. Each change to use the new API
460 is often "obvious" and can be committed without review. Once the new API
461 is in place and used, it is much easier to replace the underlying
462 implementation of the API. This implementation change is logically
463 separate from the API change.</li>
466 <p>If you are interested in making a large change, and this scares you, please
467 make sure to first <a href="#newwork">discuss the change/gather consensus</a>
468 then ask about the best way to go about making the change.</p>
471 <!-- _______________________________________________________________________ -->
472 <div class="doc_subsection"><a name="attribution">Attribution of
474 <div class="doc_text">
475 <p>We believe in correct attribution of contributions to their contributors.
476 However, we do not want the source code to be littered with random
477 attributions "this code written by J. Random Hacker" (this is noisy and
478 distracting). In practice, the revision control system keeps a perfect
479 history of who changed what, and the CREDITS.txt file describes higher-level
480 contributions. If you commit a patch for someone else, please say "patch
481 contributed by J. Random Hacker!" in the commit message.</p>
483 <p>Overall, please do not add contributor names to the source code.</p>
486 <!--=========================================================================-->
487 <div class="doc_section">
488 <a name="clp">Copyright, License, and Patents</a>
490 <!--=========================================================================-->
492 <div class="doc_text">
493 <p>This section addresses the issues of copyright, license and patents for the
494 LLVM project. Currently, the University of Illinois is the LLVM copyright
495 holder and the terms of its license to LLVM users and developers is the
496 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">University of
497 Illinois/NCSA Open Source License</a>.</p>
499 <div class="doc_notes">
500 <p style="text-align:center;font-weight:bold">NOTE: This section deals with
501 legal matters but does not provide legal advice. We are not lawyers, please
502 seek legal counsel from an attorney.</p>
506 <!-- _______________________________________________________________________ -->
507 <div class="doc_subsection"><a name="copyright">Copyright</a></div>
508 <div class="doc_text">
509 <p>For consistency and ease of management, the project requires the copyright
510 for all LLVM software to be held by a single copyright holder: the University
511 of Illinois (UIUC).</p>
513 <p>Although UIUC may eventually reassign the copyright of the software to
514 another entity (e.g. a dedicated non-profit "LLVM Organization") the intent
515 for the project is to always have a single entity hold the copyrights to LLVM
516 at any given time.</p>
518 <p>We believe that having a single copyright holder is in the best interests of
519 all developers and users as it greatly reduces the managerial burden for any
520 kind of administrative or technical decisions about LLVM. The goal of the
521 LLVM project is to always keep the code open and <a href="#license">licensed
522 under a very liberal license</a>.</p>
525 <!-- _______________________________________________________________________ -->
526 <div class="doc_subsection"><a name="license">License</a></div>
527 <div class="doc_text">
528 <p>We intend to keep LLVM perpetually open source and to use a liberal open
529 source license. The current license is the
530 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">University of
531 Illinois/NCSA Open Source License</a>, which boils down to this:</p>
534 <li>You can freely distribute LLVM.</li>
536 <li>You must retain the copyright notice if you redistribute LLVM.</li>
538 <li>Binaries derived from LLVM must reproduce the copyright notice (e.g. in
539 an included readme file).</li>
541 <li>You can't use our names to promote your LLVM derived products.</li>
543 <li>There's no warranty on LLVM at all.</li>
546 <p>We believe this fosters the widest adoption of LLVM because it <b>allows
547 commercial products to be derived from LLVM</b> with few restrictions and
548 without a requirement for making any derived works also open source (i.e.
549 LLVM's license is not a "copyleft" license like the GPL). We suggest that you
550 read the <a href="http://www.opensource.org/licenses/UoI-NCSA.php">License</a>
551 if further clarification is needed.</p>
553 <p>Note that the LLVM Project does distribute llvm-gcc, <b>which is GPL.</b>
554 This means that anything "linked" into llvm-gcc must itself be compatible
555 with the GPL, and must be releasable under the terms of the GPL. This
556 implies that <b>any code linked into llvm-gcc and distributed to others may
557 be subject to the viral aspects of the GPL</b> (for example, a proprietary
558 code generator linked into llvm-gcc must be made available under the GPL).
559 This is not a problem for code already distributed under a more liberal
560 license (like the UIUC license), and does not affect code generated by
561 llvm-gcc. It may be a problem if you intend to base commercial development
562 on llvm-gcc without redistributing your source code.</p>
564 <p>We have no plans to change the license of LLVM. If you have questions or
565 comments about the license, please contact the
566 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a>.</p>
569 <!-- _______________________________________________________________________ -->
570 <div class="doc_subsection"><a name="patents">Patents</a></div>
571 <div class="doc_text">
572 <p>To the best of our knowledge, LLVM does not infringe on any patents (we have
573 actually removed code from LLVM in the past that was found to infringe).
574 Having code in LLVM that infringes on patents would violate an important goal
575 of the project by making it hard or impossible to reuse the code for
576 arbitrary purposes (including commercial use).</p>
578 <p>When contributing code, we expect contributors to notify us of any potential
579 for patent-related trouble with their changes. If you or your employer own
580 the rights to a patent and would like to contribute code to LLVM that relies
581 on it, we require that the copyright owner sign an agreement that allows any
582 other user of LLVM to freely use your patent. Please contact
583 the <a href="mailto:llvm-oversight@cs.uiuc.edu">oversight group</a> for more
587 <!-- _______________________________________________________________________ -->
588 <div class="doc_subsection"><a name="devagree">Developer Agreements</a></div>
589 <div class="doc_text">
590 <p>With regards to the LLVM copyright and licensing, developers agree to assign
591 their copyrights to UIUC for any contribution made so that the entire
592 software base can be managed by a single copyright holder. This implies that
593 any contributions can be licensed under the license that the project
596 <p>When contributing code, you also affirm that you are legally entitled to
597 grant this copyright, personally or on behalf of your employer. If the code
598 belongs to some other entity, please raise this issue with the oversight
599 group before the code is committed.</p>
602 <!-- *********************************************************************** -->
605 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
606 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
607 <a href="http://validator.w3.org/check/referer"><img
608 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
610 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a><br>
611 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
612 Last modified: $Date$