llvm-svn: 49042

start of a filename, not a filename+length.  All clients can produce a
null terminated name, and the system api's require null terminated 
strings anyway.

llvm-svn: 49041

llvm-svn: 49040

llvm-svn: 49037

llvm-svn: 49036

llvm-svn: 49035

provides fast MappedFile::getFile for large files.

llvm-svn: 49034

llvm-svn: 49033

The new MemoryBuffer doesn't "leak" file descriptors and handles the
small file case efficiently.

llvm-svn: 49032

1) stop using MappedFile.
2) if profitable use the sys::path::MapInFilePages api to
   read the file.
3) otherwise fallback to read.

When sys::path::MapInFilePages is implemented, this provides
several benefits:

#1: this avoids fragmenting memory for small files.
#2: this avoids extraneous stat calls when the file size is known.
#3: this only keeps the file descriptor open while reading the 
    file, not for the duration of the lifetime of the memory 
    buffer.  This fixes a serious clang FD 'leak' problem.

I believe that this will work on a win32 machine, but I don't have
one to test on.  I'd appreciate it if someone could check.

llvm-svn: 49031

llvm-svn: 49030

MemoryBuffer is higher level and more closely matches the model
needed.

llvm-svn: 49029

llvm-svn: 49028

llvm-svn: 49027

llvm-svn: 49026

make getBase() return a const-correct pointer.

llvm-svn: 49025

not an mmapped file.  This more closely matches its requirements and
provides an implicitly null terminated buffer, something this
routine had to emulate itself before.

llvm-svn: 49024

llvm-svn: 49023

and shared.  This complicates the design, is not used, and probably
doesn't even work.

llvm-svn: 49022

llvm-svn: 49021

llvm-svn: 49020

llvm-svn: 49016

llvm-svn: 49014

llvm-svn: 49013

llvm-svn: 49012

llvm-svn: 49011

llvm-svn: 49010

tons of out of date comments (really nothing throws here!) and fixes
some other fairly glaring issues: "size" used to return the size of 
the file *and* change it, depending on how you called it.

llvm-svn: 49009

llvm-svn: 49008

not marked nounwind, or for all functions when -enable-eh
is set, provided the target supports Dwarf EH.

llvm-gcc generates nounwind in the right places; other FEs
will need to do so also.  Given such a FE, -enable-eh should
no longer be needed.

llvm-svn: 49006

llvm-svn: 49005

llvm-svn: 49004

EH info for these functions causes the tests to fail for
random reasons (e.g. looking for 'or' or counting lines
with asm-printer; labels count as lines.)

llvm-svn: 49003

llvm-svn: 49002

llvm-svn: 49001

crash miscompilations.

llvm-svn: 49000

not the end.

llvm-svn: 48999

llvm-svn: 48998

llvm-svn: 48997

a PathDiagnosticClient.

llvm-svn: 48996