nnesse/minwin-gcc-5-2: A patched gcc 5.2 enabling a new 'minwin' target that does not link to the Microsoft C library.

Niels Nesse eb72d50f44 Import gcc 5.2.0 from tarball		9 年之前
..
asan	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
include	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
interception	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
libbacktrace	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
lsan	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
sanitizer_common	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
tsan	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
ubsan	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
ChangeLog	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
LICENSE.TXT	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
MERGE	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
Makefile.am	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
Makefile.in	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
README.gcc	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
acinclude.m4	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
aclocal.m4	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
config.h.in	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
configure	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
configure.ac	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
configure.tgt	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
libsanitizer.spec.in	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
libtool-version	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前
merge.sh	eb72d50f44 Import gcc 5.2.0 from tarball	9 年之前

		
			
			
				README.gcc
			
		
		
	
			
				AddressSanitizer (http://code.google.com/p/address-sanitizer) and
ThreadSanitizer (http://code.google.com/p/thread-sanitizer/) are
projects initially developed by Google Inc.
Both tools consist of a compiler module and a run-time library.
The sources of the run-time library for these projects are hosted at
http://llvm.org/svn/llvm-project/compiler-rt in the following directories:
  include/sanitizer
  lib/sanitizer_common
  lib/interception
  lib/asan
  lib/tsan
  lib/lsan
  lib/ubsan

Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the
GCC tree.  All non-trivial changes, functionality improvements, etc. should go
through the upstream tree first and then be merged back to the GCC tree.
The merges from upstream should be done with the aid of the merge.sh script;
it will also update the file MERGE to contain the upstream revision
we merged with.

			
		