From c5cf3309a2126b626c10537eaee40d1d632f33c0 Mon Sep 17 00:00:00 2001 From: cvs2svn Date: Fri, 24 Oct 2003 20:17:46 +0000 Subject: This commit was manufactured by cvs2svn to create tag 'RELEASE_1'. git-svn-id: https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_1@9499 91177308-0d34-0410-b5e6-96231b3b80d8 --- LICENSE.TXT | 34 - README.txt | 165 +- docs/AliasAnalysis.html | 6 +- docs/CFEBuildInstrs.html | 16 +- docs/ChrisNotes.txt | 15 + docs/CodingStandards.html | 2 + docs/CommandLine.html | 2 + docs/DSGraphStatus.html | 2 + docs/FAQ.html | 17 + docs/GettingStarted.html | 44 +- docs/HowToSubmitABug.html | 2 + docs/LangRef.html | 2 + docs/OpenProjects.html | 2 + docs/ProgrammersManual.html | 2 + docs/Projects.html | 3 + docs/ReleaseNotes.html | 11 +- docs/TestingGuide.html | 2 + docs/WritingAnLLVMPass.html | 2 + docs/index.html | 265 +++ include/Config/strings.h | 23 + include/llvm/Analysis/FindUsedTypes.h | 4 + include/llvm/CodeGen/SparcRegInfo.h | 240 --- lib/Analysis/IPA/FindUsedTypes.cpp | 11 + lib/Target/CBackend/CBackend.cpp | 1384 ------------- lib/Target/SparcV9/InstrSelection/InstrForest.cpp | 332 --- .../SparcV9/InstrSelection/InstrSelection.cpp | 385 ---- .../InstrSelection/InstrSelectionSupport.cpp | 259 --- lib/Target/SparcV9/InstrSelection/Makefile | 15 - lib/Target/SparcV9/RegAlloc/IGNode.cpp | 58 - lib/Target/SparcV9/RegAlloc/IGNode.h | 118 -- lib/Target/SparcV9/RegAlloc/InterferenceGraph.cpp | 248 --- lib/Target/SparcV9/RegAlloc/InterferenceGraph.h | 70 - lib/Target/SparcV9/RegAlloc/LiveRange.h | 180 -- lib/Target/SparcV9/RegAlloc/LiveRangeInfo.cpp | 413 ---- lib/Target/SparcV9/RegAlloc/LiveRangeInfo.h | 124 -- lib/Target/SparcV9/RegAlloc/Makefile | 17 - lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp | 1380 ------------- lib/Target/SparcV9/RegAlloc/PhyRegAlloc.h | 177 -- lib/Target/SparcV9/RegAlloc/RegAllocCommon.h | 28 - lib/Target/SparcV9/RegAlloc/RegClass.cpp | 248 --- lib/Target/SparcV9/RegAlloc/RegClass.h | 142 -- lib/Target/X86/X86AsmPrinter.cpp | 1020 ---------- lib/Target/X86/X86FloatingPoint.cpp | 600 ------ lib/Target/X86/X86ISelPattern.cpp | 124 -- lib/Target/X86/X86ISelSimple.cpp | 2137 -------------------- lib/Target/X86/X86PeepholeOpt.cpp | 133 -- test/BugPoint/misopt-basictest.ll | 3 +- test/Makefile | 7 +- 48 files changed, 522 insertions(+), 9952 deletions(-) create mode 100644 docs/ChrisNotes.txt create mode 100644 docs/index.html create mode 100644 include/Config/strings.h delete mode 100644 include/llvm/CodeGen/SparcRegInfo.h delete mode 100644 lib/Target/CBackend/CBackend.cpp delete mode 100644 lib/Target/SparcV9/InstrSelection/InstrForest.cpp delete mode 100644 lib/Target/SparcV9/InstrSelection/InstrSelection.cpp delete mode 100644 lib/Target/SparcV9/InstrSelection/InstrSelectionSupport.cpp delete mode 100644 lib/Target/SparcV9/InstrSelection/Makefile delete mode 100644 lib/Target/SparcV9/RegAlloc/IGNode.cpp delete mode 100644 lib/Target/SparcV9/RegAlloc/IGNode.h delete mode 100644 lib/Target/SparcV9/RegAlloc/InterferenceGraph.cpp delete mode 100644 lib/Target/SparcV9/RegAlloc/InterferenceGraph.h delete mode 100644 lib/Target/SparcV9/RegAlloc/LiveRange.h delete mode 100644 lib/Target/SparcV9/RegAlloc/LiveRangeInfo.cpp delete mode 100644 lib/Target/SparcV9/RegAlloc/LiveRangeInfo.h delete mode 100644 lib/Target/SparcV9/RegAlloc/Makefile delete mode 100644 lib/Target/SparcV9/RegAlloc/PhyRegAlloc.cpp delete mode 100644 lib/Target/SparcV9/RegAlloc/PhyRegAlloc.h delete mode 100644 lib/Target/SparcV9/RegAlloc/RegAllocCommon.h delete mode 100644 lib/Target/SparcV9/RegAlloc/RegClass.cpp delete mode 100644 lib/Target/SparcV9/RegAlloc/RegClass.h delete mode 100644 lib/Target/X86/X86AsmPrinter.cpp delete mode 100644 lib/Target/X86/X86FloatingPoint.cpp delete mode 100644 lib/Target/X86/X86ISelPattern.cpp delete mode 100644 lib/Target/X86/X86ISelSimple.cpp delete mode 100644 lib/Target/X86/X86PeepholeOpt.cpp diff --git a/LICENSE.TXT b/LICENSE.TXT index 91d27b507b..ec389f3176 100644 --- a/LICENSE.TXT +++ b/LICENSE.TXT @@ -1,37 +1,3 @@ -NOTICE: -======= -All distributions of LLVM prior to the 1.0 Release will be licensed to you -under the LLVM pre-release license. The 1.0 Release will be announced on the -LLVM Announcements Mailing List. - -After the 1.0 Release of LLVM, the LLVM code will be licensed to you under the -LLVM Release License (aka the Illinois Open Source License). - -The main point is that you cannot re-distribute LLVM until the 1.0 Release. - -============================================================================== -LLVM pre-release license -============================================================================== - -This is a pre-release distribution of the LLVM software and is provided for -evaluation only. This version of the LLVM software or modifications thereof -should not be distributed to third parties for any purpose. Any third parties -interested in it can request a copy directly by sending e-mail to -llvmdev@cs.uiuc.edu. As this is an evaluation release, we would appreciate any -and all feedback, ideas, and reports of bugs that you encounter. You may -discuss development of LLVM on llvmdev@cs.uiuc.edu, and bugs can be submitted -through the LLVM Bug Tracker at http://llvm.cs.uiuc.edu/bugzilla/ . We thank -you for your interest in LLVM and look forward to any comments or feedback you -may have. - -THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS -FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE -SOFTWARE. - ============================================================================== LLVM Release License ============================================================================== diff --git a/README.txt b/README.txt index 60fd024e62..af2973214d 100644 --- a/README.txt +++ b/README.txt @@ -1,106 +1,129 @@ + The LLVM Compiler Infrastructure + http://llvm.cs.uiuc.edu + Welcome to LLVM! +----------------- +This file is intended to do four things: +(1) help you get started using LLVM; +(2) tell you how to get questions about LLVM answered; +(3) tell you where to find documentation for different kinds of questions; and +(4) tell you about three LLVM-related mailing lists. -This file provides the location of all important LLVM documentation. In -particular, you should read the license information and the installation -directions before you begin using LLVM. -After that, there are several technical references that will help you use LLVM. -Consult them as necessary. +Getting Started with LLVM +------------------------- -Finally, you can find information on how to communicate with the LLVM -developers and LLVM community. This is of primary interest if you wish to -submit a bug, supply a patch, or just keep current with what's going on with -LLVM. +(1) For license information: + llvm/LICENSE.txt -Introductory Literature: +(2) Installing and compiling LLVM: + llvm/docs/GettingStarted.html - LLVM Home Page: - http://llvm.cs.uiuc.edu +(3) Learn about features and limitations of this release: + llvm/docs/ReleaseNotes.html - License Information: - llvm/LICENSE.txt +(4) Learn how to write a pass within the LLVM system: + llvm/docs/WritingAnLLVMPass.html - Release Notes: - llvm/docs/ReleaseNotes.html +(5) Learn how to start a new development project using LLVM, where your + new source code can live anywhere (outside or inside the LLVM tree), + while using LLVM header files and libraries: + llvm/docs/Projects.html -LLVM Design: - The LLVM Instruction Set and Compilation Strategy: - http://llvm.cs.uiuc.edu/pubs/2002-08-09-LLVMCompilationStrategy.html +Getting Help with LLVM +---------------------- -LLVM User Guides: +(1) If you have questions or development problems not answered in the + documentation, send e-mail to llvmdev@cs.uiuc.edu. This mailing list is + monitored by all the people in the LLVM group at Illinois, and you should + expect prompt first responses. - Download and Installation Instructions: - llvm/docs/GettingStarted.html +(2) To report a bug, submit a bug report as described in the document: + http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html - LLVM Command Guide: - llvm/docs/CommandGuide/CommandGuide.html +(3) We now use Bugzilla to track bugs, so you can check the status of + previous bugs at: + http://llvm.cs.uiuc.edu/bugs/query.cgi - LLVM Assembly Language: - llvm/docs/LangRef.html - LLVM Test Suite Guide: - llvm/docs/TestingGuide.html +LLVM Documentation +------------------ -LLVM Programming Documentation: +All the documents mentioned below except the design overview tech report +are included as part of the LLVM release (in llvm/docs/*): + +LLVM Design Overview: + LLVM : A Compilation Framework for Lifelong Program Analysis + and Transformation: + http://llvm.cs.uiuc.edu/pubs/2003-09-30-LifelongOptimizationTR.html + +LLVM User Guides: + + Download and Installation Instructions: + llvm/docs/GettingStarted.html + + LLVM Command Guide: + llvm/docs/CommandGuide/index.html - LLVM Programmers Manual: - llvm/docs/ProgrammersManual.html + LLVM Assembly Language: + llvm/docs/LangRef.html - Writing an LLVM Pass: - llvm/docs/WritingAnLLVMPass.html + LLVM Test Suite Guide: + llvm/docs/TestingGuide.html + +LLVM Programming Documentation: - Alias Analysis in LLVM: - llvm/docs/AliasAnalysis.html + LLVM Programmers Manual: + llvm/docs/ProgrammersManual.html - Command Line Library: - llvm/docs/CommandLine.html + Writing an LLVM Pass: + llvm/docs/WritingAnLLVMPass.html - Coding Standards: - llvm/docs/CodingStandards.html + Alias Analysis in LLVM: + llvm/docs/AliasAnalysis.html -LLVM Community: + Command Line Library: + llvm/docs/CommandLine.html - Submitting a Bug: - http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html + Coding Standards: + llvm/docs/CodingStandards.html - Open Projects: - llvm/docs/OpenProjects.html +Other LLVM Resources: - Creating a new LLVM Project: - llvm/docs/Projects.html + Submitting a Bug: + http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html - Mailing Lists: - There are several mailing lists providing LLVM users with - information: + Open Projects: + llvm/docs/OpenProjects.html - o LLVM Announcements List: - http://mail.cs.uiuc.edu/mailman/listinfo/llvm-announce + Creating a new LLVM Project: + llvm/docs/Projects.html - This is a low volume list that provides - important announcements regarding LLVM. It is - primarily intended to announce new releases, - major updates to the software, etc. This list - is highly recommended for anyone that uses LLVM. +Mailing Lists +-------------- +There are three mailing lists for providing LLVM users with information: +(1) LLVM Announcements List: + http://mail.cs.uiuc.edu/mailman/listinfo/llvm-announce - o LLVM Developers List: - http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev + This is a low volume list that provides important announcements regarding + LLVM. It is primarily intended to announce new releases, major updates to + the software, etc. This list is highly recommended for anyone that uses + LLVM. - This list is for people who want to be included - in technical discussions of LLVM. People post - to this list when they have questions about - writing code for or using the LLVM tools. It - is low volume. +(2) LLVM Developers List: + http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev - o LLVM Commits List - http://mail.cs.uiuc.edu/mailman/listinfo/llvm-commits + This list is for people who want to be included in technical discussions + of LLVM. People post to this list when they have questions about writing + code for or using the LLVM tools. It is relatively low volume. - This list contains all commit messages that are - made when LLVM developers commit code changes - to the CVS archive. It is useful for those who - want to stay on the bleeding edge of LLVM - development. +(3) LLVM Commits List + http://mail.cs.uiuc.edu/mailman/listinfo/llvm-commits - This list is very high volume. + This list contains all commit messages that are made when LLVM developers + commit code changes to the CVS archive. It is useful for those who want to + stay on the bleeding edge of LLVM development. This list is very high + volume. diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html index e4bebca8aa..921fabc5aa 100644 --- a/docs/AliasAnalysis.html +++ b/docs/AliasAnalysis.html @@ -494,10 +494,12 @@ printed. -
+
+
Chris Lattner
+The LLVM Compiler Infrastructure +
Last modified: $Date$ - diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html index 080153fe8c..5e753ab992 100644 --- a/docs/CFEBuildInstrs.html +++ b/docs/CFEBuildInstrs.html @@ -15,9 +15,12 @@ C/C++ front-end, based on GCC 3.4, from source.

NOTE: This is currently a somewhat fragile, error-prone -process, and you should only try to do it if (A) you really, really, -really can't use the binaries we distribute, and (B) you are a wicked -good GCC hacker.

+process, and you should only try to do it if +

We welcome patches to help make this process simpler.

@@ -105,6 +108,11 @@ good GCC hacker.

  • No inline assembly for position independent code. At the LLVM level, everything is position independent.
  • We handle .init and .fini differently.
    • +
  • You may have to disable multilib support in your target. Using multilib + support causes the GCC compiler driver to add a lot of "-L" + options to the link line, which do not relate to LLVM and confuse + gccld. To disable multilibs, delete any + MULTILIB_OPTIONS lines from your target files.
  • Did we mention that we don't support inline assembly? You'll probably have to add some fixinclude hacks to disable it in the system headers.
    • @@ -149,6 +157,8 @@ following means:

    Brian Gaeke
    +The LLVM Compiler Infrastructure +
    Last modified: $Date$     diff --git a/docs/ChrisNotes.txt b/docs/ChrisNotes.txt new file mode 100644 index 0000000000..ef75ed919f --- /dev/null +++ b/docs/ChrisNotes.txt @@ -0,0 +1,15 @@ +* Rewrite the llvm parser/lexer in http://www.antlr.org when time permits. + They actually do C++. Imagine that. +* Need a way to attach bytecode block info at various levels of asm code. +* Recognize and save comments in assembly and bytecode format +* Encode line number table in bytecode (like #line), optional table + +* Encode negative relative offsets in the bytecode file + +* Apparently bison has a %pure_parser option. Maybe useful for AsmParser + +* Implement the following derived types: + * "packed format", like this: [4 x sbyte]: Packed SIMD datatype +* Bytecode reader should use extensions that may or may not be linked into the + application to read blocks. Thus an easy way to ignore symbol table info + would be to not link in that reader into the app. diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html index d469d6315e..668f4ec626 100644 --- a/docs/CodingStandards.html +++ b/docs/CodingStandards.html @@ -831,6 +831,8 @@ something. :)
    Chris Lattner
    +The LLVM Compiler Infrastructure +
    Last modified: Sun Oct 12 22:12:43 CDT 2003 diff --git a/docs/CommandLine.html b/docs/CommandLine.html index a418dcba45..390ca237e0 100644 --- a/docs/CommandLine.html +++ b/docs/CommandLine.html @@ -1530,6 +1530,8 @@ line options