LLVM backend for 6502
Go to file
Chris Lattner 76a1bf9eb9 The levelraise pass is a broken old piece of crufty code that should be
left on the side of the road without a second thought.

It is preventing forward progress, so for now, we will disable it by default.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@9140 91177308-0d34-0410-b5e6-96231b3b80d8
2003-10-15 21:48:38 +00:00
autoconf Adding additional license information to these files. 2003-10-13 20:34:27 +00:00
docs Updated some of the information for the new autoconf changes. 2003-10-15 16:52:57 +00:00
examples/ModuleMaker Checkin of autoconf-style object root. 2003-09-06 15:03:24 +00:00
include Remove usage of use_size() 2003-10-15 16:43:24 +00:00
lib Fix up error message. 2003-10-15 20:46:58 +00:00
projects Checkin of autoconf-style object root. 2003-09-06 15:03:24 +00:00
runtime Adding additional license information to these files. 2003-10-13 20:34:27 +00:00
test New testcase which the inliner breaks 2003-10-14 01:04:12 +00:00
tools The levelraise pass is a broken old piece of crufty code that should be 2003-10-15 21:48:38 +00:00
utils Fix bug in script 2003-10-14 01:22:08 +00:00
.cvsignore Ok, try #2, this time I'll not be stupid 2003-08-03 18:33:24 +00:00
configure Added a macro and code that checks for the %a format string in sprintf(). 2003-10-13 16:22:01 +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 Added a link to the main page for LLVM. 2003-10-13 21:09:04 +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:
	LLVM Home Page:
		http://llvm.cs.uiuc.edu

	License Information:
		llvm/LICENSE.txt

	Downloading and 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:
	http://llvm.cs.uiuc.edu/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.