Go to file
Duncan Sands 3a02f3eeff GCC 4.4 warns that Receiver may be used uninitialized in this function.
As far as I can see, gcc is right to think this!  The following change
will cause a nice segfault rather than undefined behaviour if this case
occurs.  Someone who understands what this code is supposed to do should
probably take a proper look.

llvm-svn: 116917
2010-10-20 08:21:16 +00:00
clang GCC 4.4 warns that Receiver may be used uninitialized in this function. 2010-10-20 08:21:16 +00:00
compiler-rt make: Add CheckCommandLineOverrides to my little Makefile library, a routine for 2010-10-14 21:23:37 +00:00
debuginfo-tests testcase commit for upcoming fix. 2010-09-21 20:51:54 +00:00
libcxx atomic_schar, atomic_uchar, atomic_short, atomic_ushort, atomic_int, atomic_uint, atomic_long, atomic_ulong, atomic_llong, atomic_ullong, atomic_char16_t, atomic_char32_t and atomic_wchar_t. 2010-10-19 21:22:10 +00:00
lldb Don't re-insert disabled breakpoint locations. 2010-10-20 03:36:33 +00:00
llvm Fix a TODO by removing some unnecesary copies. 2010-10-20 08:02:24 +00:00