6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-07-19 03:29:22 +00:00
Code Issues Projects Releases Wiki Activity
8f74680c78
llvm-6502/runtime/GCCLibraries/crtend
History
Reid Spencer 19b7e0e0ca For PR786: 
Minor tweaks in public headers and a few .cpp files so that LLVM can build
successfully with -pedantic and projects using LLVM with -pedantic don't
get warnings from LLVM. There's still more -pedantic warnings to fix.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@28453 91177308-0d34-0410-b5e6-96231b3b80d8
2006-05-24 19:21:13 +00:00
..
comp_genericeh.lst Rewrite makefile logic to build an archive instead of a .o file. This is 2003-11-29 10:05:30 +00:00
comp_main.lst Rewrite makefile logic to build an archive instead of a .o file. This is 2003-11-29 10:05:30 +00:00
comp_sjljeh.lst Rewrite makefile logic to build an archive instead of a .o file. This is 2003-11-29 10:05:30 +00:00
crtend.c Make the new and old front-ends more similar: now neither uses __main. 2006-03-09 06:16:28 +00:00
Exception.cpp Fix wierd problems linking C programs which look for symbols in libstdc++. 2003-11-08 05:13:40 +00:00
Exception.h For PR786: 2006-05-24 19:21:13 +00:00
Makefile Make the new and old front-ends more similar: now neither uses __main. 2006-03-09 06:16:28 +00:00
README.txt Make the new and old front-ends more similar: now neither uses __main. 2006-03-09 06:16:28 +00:00
SJLJ-Exception.cpp Remove trailing whitespace 2005-04-21 23:48:37 +00:00
SJLJ-Exception.h Remove trailing whitespace 2005-04-21 23:48:37 +00:00

README.txt 

This directory contains the C and C++ runtime libraries for the LLVM GCC
front-ends.  It is composed of four distinct pieces:

1. __main: now dead, but provided for compatibility.

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.