llvm-svn: 112921

llvm-svn: 112920

llvm-svn: 112919

The rationale behind this is that it is normal for callback functions to have a non-void return type
and it should still be possible to mark them noreturn. (JavaScriptCore is a good example of this).

llvm-svn: 112918

llvm-svn: 112917

to set up a destructor call, because ABIs can tweak these conventions.
Fixes rdar://problem/8386802.

llvm-svn: 112916

(original patch r112791 was reverted due to a bug).

llvm-svn: 112915

using the same methods as used for normal structures.
 - This fixes problems with reading past the end of the structure and with
   handling straddled bit-field access.

llvm-svn: 112914

functions.

llvm-svn: 112913

stores.

llvm-svn: 112912

llvm-svn: 112910

Reapply 112850 and 112839 with a constructor for the BinaryOperatorData struct. Clang would zero out the enum and pointer in the struct in some conditions, but GCC would never zero out the values.

llvm-svn: 112909

two regressions in Boost.Config.

llvm-svn: 112908

llvm-svn: 112907

#uses comments, with a testcase.

llvm-svn: 112906

llvm-svn: 112905

not a scrunched version of it.

llvm-svn: 112904

llvm-svn: 112903

Patch by Cameron Esfahani!

llvm-svn: 112902

comments, these don't happen anymore.

llvm-svn: 112901

Thanks Chris!

llvm-svn: 112900

Remove #uses comments from functions: they we're padded out to column 50
and were potentially confusing for externally visible functions.

going further, remove the "<i8**> [#uses=3]" comments entirely. They
add a lot of noise, confuse people about what the IR is, and don't add 
any particular value.  When the types are long it makes it really really
hard to read IR.

If someone is interested in this sort of thing, the right way to do this
is to implement an AsmAnnotationWriter that produces the same output, and
add a flag to llvm-dis (only) to produce this output.

llvm-svn: 112899

llvm-svn: 112898

make it clear what they're testing so there is no way to know it's right
or to update it.

llvm-svn: 112897

llvm-svn: 112896

llvm-svn: 112895

and were potentially confusing for externally visible functions.

going further, remove the "<i8**> [#uses=3]" comments entirely. They
add a lot of noise, confuse people about what the IR is, and don't add 
any particular value.  When the types are long it makes it really really
hard to read IR.

If someone is interested in this sort of thing, the right way to do this
is to implement an AsmAnnotationWriter that produces the same output, and
add a flag to llvm-dis (only) to produce this output.

llvm-svn: 112894

llvm-svn: 112892

llvm-svn: 112891

Radar 8388233

llvm-svn: 112890

llvm-svn: 112889

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

llvm-svn: 112887

llvm-svn: 112886

llvm-svn: 112885

code. Also, teach it about explicitly-specified template arguments.

llvm-svn: 112884

large local stack areas or require dynamic stack realignment, allocate a
base register via which to access the local frame. This allows efficient
access to frame indices not accessible via the FP (either due to being out
of range or due to dynamic realignment) or the SP (due to variable sized
object allocation). In particular, this greatly improves efficiency of access
to spill slots in Thumb functions which contain VLAs.

rdar://7352504
rdar://8374540
rdar://8355680

llvm-svn: 112883

experiment in a few days.

llvm-svn: 112882

- Add patterns to match the following MMX builtins:

   * __builtin_ia32_vec_init_v8qi
   * __builtin_ia32_vec_init_v4hi
   * __builtin_ia32_vec_init_v2si
   * __builtin_ia32_vec_ext_v2si

  These builtins do not correspond to a single MMX instruction. They will have
  to be lowered -- most likely in the back-end.

llvm-svn: 112881

Also changed the expected strings to be matched since "thread list" changed its
output format. 

llvm-svn: 112880