LLVM backend for 6502
Go to file
John Criswell b96646f1f5 Removed information on common build problems. That is now documented in
the FAQ (FAQ.html).


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9087 91177308-0d34-0410-b5e6-96231b3b80d8
2003-10-13 16:16:25 +00:00
autoconf The code that called strsignal is toast. 2003-10-10 17:04:43 +00:00
docs Removed information on common build problems. That is now documented in 2003-10-13 16:16:25 +00:00
examples/ModuleMaker Checkin of autoconf-style object root. 2003-09-06 15:03:24 +00:00
include Extricate the "reverse" support from the depth-first iterator. This is really 2003-10-13 15:45:33 +00:00
lib Stop using "reverse depth first" order 2003-10-13 15:21:58 +00:00
projects Checkin of autoconf-style object root. 2003-09-06 15:03:24 +00:00
runtime Actually pass in a pointer to the thrown object, not a pointer to the 2003-10-10 22:55:55 +00:00
test make the indvar obviously non-canonical 2003-10-13 03:31:42 +00:00
tools Don't include <stdlib.h>. 2003-10-10 19:12:45 +00:00
utils Regularize header file comments 2003-10-13 03:32:08 +00:00
.cvsignore Ok, try #2, this time I'll not be stupid 2003-08-03 18:33:24 +00:00
configure Added the eon and perlbmk benchmarks. 2003-10-10 01:11:54 +00:00
CREDITS.TXT Add more credits 2003-10-07 20:50:29 +00:00
LICENSE.TXT Add prerelease license to cvs 2003-06-04 19:46:36 +00:00
Makefile I really meant to use that AUTOHEADER variable I put in there. 2003-10-08 21:38:35 +00:00
Makefile.common Checkin of autoconf-style object root. 2003-09-06 14:44:17 +00:00
Makefile.config.in Fixed SPEC so that it would run correctly with the new autoconf-style object 2003-09-11 18:03:50 +00:00
Makefile.rules Print out just the filename being compiled/linked, not the full path to it. 2003-10-10 17:37:22 +00:00
README.txt Master README file that points to all other documentation. 2003-10-13 15:59:28 +00:00

Welcome to LLVM!

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.

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.

Introductory Literature:
	License Information:
		llvm/LICENSE.txt

	Installation Instructions:
		llvm/docs/GettingStarted.html

	Release Notes:
		llvm/docs/ReleaseNotes.html

Technical Reference:
	Command Documentation:
		llvm/docs/CommandGuide/CommandGuide.html

	Using the LLVM Test Suite:
		llvm/docs/TestingGuide.html

	LLVM Assembly Language:
		llvm/docs/LangRef.html

	LLVM Source Code Tree:
		llvm/docs/ProgrammersManual.html

	Coding Standards:
		llvm/docs/CodingStandards.html

LLVM Community:
	Submitting a Bug:
		llvm/docs/HowToSubmitABug.html

	Mailing Lists:
		There are several mailing lists providing LLVM users with information:

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


			o 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 low volume.

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