6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-26 21:32:10 +00:00
Code Issues Projects Releases Wiki Activity

Add readme and spiff up makefile header

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@10254 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2003-11-29 09:22:53 +00:00
parent b895fb06ec
commit e893d649fa
2 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
runtime/GCCLibraries/crtend/Makefile
View File

@ -1,4 +1,4 @@
##===- runtime/GCCLibraries/crtend/Makefile ------------------------------*- Makefile -*-===## ##===- runtime/GCCLibraries/crtend/Makefile ----------------*- Makefile -*-===##
# #
# The LLVM Compiler Infrastructure # The LLVM Compiler Infrastructure
# #
@ -6,6 +6,12 @@
# the University of Illinois Open Source License. See LICENSE.TXT for details. # the University of Illinois Open Source License. See LICENSE.TXT for details.
# #
##===----------------------------------------------------------------------===## ##===----------------------------------------------------------------------===##
#
# This directory contains the C and C++ runtime libraries for the LLVM GCC
# front-ends.
#
##===----------------------------------------------------------------------===##
LEVEL = ../../.. LEVEL = ../../..
BYTECODE_LIBRARY=1 BYTECODE_LIBRARY=1
DONT_BUILD_RELINKED=1 DONT_BUILD_RELINKED=1

15
runtime/GCCLibraries/crtend/README.txt Normal file
View File

@ -0,0 +1,15 @@
This directory contains the C and C++ runtime libraries for the LLVM GCC
front-ends. It is composed of four distinct pieces:
1. __main and static ctor/dtor support. This is used by both C and C++ codes.
2. Generic EH support routines. This is used by C/C++ programs that use
setjmp/longjmp, and by C++ programs that make use of exceptions.
3. setjmp/longjmp EH support. This is used by C/C++ programs that call SJLJ.
4. C++ exception handling runtime support.
These four components are compiled together into an archive file, so that
applications using a subset of the four do not pull in unnecessary code and
dependencies.