llvm-svn: 114999

also fixes PR8250.

llvm-svn: 114972

llvm-svn: 114847

llvm-svn: 114839

llvm-svn: 114832

Cameron Esfahani, tweaked to use array_lengthof.

llvm-svn: 114073

with attribute warn_unused_result" here - suppress the warning harder.

llvm-svn: 114072

llvm-svn: 113235

teach LazyValueInfo to use them.

llvm-svn: 113196

Fix zeroExtend and signExtend to support empty sets, and to return the smallest
possible result set which contains the extension of each element in their
inputs. For example zext i8 [100, 10) to i16 is now [0, 256), not i16 [100, 10)
which contains 63446 members.

llvm-svn: 113187

I wasn't able to convince myself that all GetMainExecutable
implementations always return absolute paths; this prevents
unexpected behavior in case they ever don't.

llvm-svn: 112888

capacity and remove the workaround in SmallVector<T,0>.  There are some
theoretical benefits to a N->2N+1 growth policy anyway.

llvm-svn: 112870

bugpoint uses it.

llvm-svn: 112803

of a base class.

This makes it possible to unregister the file from FilesToRemove when
the file is done. Also, this eliminates the need for
formatted_tool_output_file.

llvm-svn: 112706

Triple class constructor.  Only valid triples should now be used
inside LLVM - front-ends are now responsable for rejecting or
correcting invalid target triples.  The Triple::normalize method
can be used to straighten out funky triples provided by users.
Give this a whirl through the buildbots to see if I caught all
places where triples enter LLVM.

llvm-svn: 112470

llvm-svn: 112189

Do unsigned char comparisons in StringRef::compare_lower to be more consistent with compare in corner cases.

llvm-svn: 112185

llvm-svn: 111993

- Cache used characters in a bitset to reduce memory overhead to just 32 bytes.
- On my core2 this code is faster except when the checked string was very short
  (smaller than the list of delimiters).

llvm-svn: 111817

llvm-svn: 111669

llvm-svn: 111661

pending output errors are detected.

llvm-svn: 111643

outside of outs() and errs() themselves, and they don't really
need custom classes.

llvm-svn: 111642

class which is using it.

llvm-svn: 111639

functionality that most command-line tools need: ensuring that the
output file gets deleted if the tool is interrupted or encounters an
error.

llvm-svn: 111595

llvm-svn: 111534

constructed with an output filename of "-". In particular, allow the
file descriptor to be closed, and close the file descriptor in the
destructor if it hasn't been explicitly closed already, to ensure
that any write errors are detected.

llvm-svn: 111436

llvm-svn: 111432

llvm-svn: 111339

llvm-svn: 111337

llvm-svn: 111325

(e.g. errs()) fails in close() due to (e.g.) a broken pipe.  As
previously written, the had_error() flag would get set and then
the raw_ostream dtor would report a fatal error.  There is nothing
the client can do about this and we have no way to report the error,
so just eat it.

llvm-svn: 111321

into report_fatal_error.  Just blast the string to stderr with write(2)
and hope for the best!  Part of rdar://8318441

llvm-svn: 111320

CrashRecovery: Clear the current context on the first crash, to avoid re-entering it if the cleanup code crashes.

llvm-svn: 111309

CrashRecovery: Add CrashRecoveryContext::GetCurrent(), so clients can find the active context from anywhere.

llvm-svn: 111308

llvm-svn: 111307

llvm-svn: 111254

implementations of equality comparison and hash computation. This
can be used to optimize node lookup by avoiding creating lots of
temporary ID values just for hashing and comparison purposes.

llvm-svn: 111130

with FoldingSetTrait::Profile.

llvm-svn: 111127

target triple and straightens it out.  This does less than gcc's script
config.sub, for example it turns i386-mingw32 into i386--mingw32 not
i386-pc-mingw32, but it does a decent job of turning funky triples into
something that the rest of the Triple class can understand.  The plan
is to use this to canonicalize triple's when they are first provided
by users, and have the rest of LLVM only deal with canonical triples.
Once this is done the special case workarounds in the Triple constructor
can be removed, making the class more regular and easier to use.  The
comments and unittests for the Triple class are already adjusted in this
patch appropriately for this brave new world of increased uniformity.

llvm-svn: 110909