aboutsummaryrefslogtreecommitdiff
path: root/README.txt
blob: fdc4b74a1b153bf7559eb2f8bc1e9428e65916e4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
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.


Getting Started with LLVM
-------------------------

(1) For license information:
        llvm/LICENSE.txt

(2) Installing and compiling LLVM:
        llvm/docs/GettingStarted.html

(3) Learn about features and limitations of this release:
        llvm/docs/ReleaseNotes.html

(4) Learn how to write a pass within the LLVM system:
        llvm/docs/WritingAnLLVMPass.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


Getting Help with LLVM
----------------------

(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.

(2) To report a bug, submit a bug report as described in the document:
		http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html

(3) We now use Bugzilla to track bugs, so you can check the status of
    previous bugs at:
	     <FIXME: WHERE DO THEY GO???>


LLVM Documentation
------------------

All the documents mentioned below except the design overview tech report
are include 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/CommandGuide.html

	LLVM Assembly Language:
		llvm/docs/LangRef.html

	LLVM Test Suite Guide:
		llvm/docs/TestingGuide.html

LLVM Programming Documentation:

	LLVM Programmers Manual:
		llvm/docs/ProgrammersManual.html

	Writing an LLVM Pass:
		llvm/docs/WritingAnLLVMPass.html

	Alias Analysis in LLVM:
		llvm/docs/AliasAnalysis.html

	Command Line Library:
		llvm/docs/CommandLine.html

	Coding Standards:
		llvm/docs/CodingStandards.html

Other LLVM Resources:

	Submitting a Bug:
		http://llvm.cs.uiuc.edu/docs/HowToSubmitABug.html

	Open Projects:
		llvm/docs/OpenProjects.html

	Creating a new LLVM Project:
		llvm/docs/Projects.html

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

    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.

(2) LLVM Developers List:
    http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev

    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.

(3) LLVM Commits List
    http://mail.cs.uiuc.edu/mailman/listinfo/llvm-commits

   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.