OpenBSD's stack smashing protection differs slightly from other
platforms:

  1. The smash handler function is "__stack_smash_handler(const char
     *funcname)" instead of "__stack_chk_fail(void)".

  2. There's a hidden "long __guard_local" object that gets linked
     into each executable and DSO.

Patch by Matthew Dempsky.

llvm-svn: 183533

As a bonus this reduces the loop from O(n^2) to O(n).

llvm-svn: 183532

llvm-svn: 183528

Avoids unused variable warnings in Release builds.

llvm-svn: 183512

llvm-svn: 183495

the internals of TargetMachine could change.

No functionality change intended.

llvm-svn: 183494

the internals of TargetMachine could change.

llvm-svn: 183493

the internals of TargetMachine could change.

llvm-svn: 183492

the internals of TargetMachine could change.

llvm-svn: 183491

the internals of TargetMachine could change.

llvm-svn: 183490

[objc-arc] Ensure that the cfg path count does not overflow when we multiply TopDownPathCount/BottomUpPathCount.

rdar://12480535

llvm-svn: 183489

the internals of TargetMachine could change.

llvm-svn: 183488

These objects are internal to the TargetMachine object and may change.

llvm-svn: 183485

Use the correct DIType when creating vector types.

llvm-svn: 183484

llvm-svn: 183477

Reapply 183271.

llvm-svn: 183472

Reapply 183270 again (because three is a magic number).

This should now no longer seg fault after r183459.

llvm-svn: 183464

llvm-svn: 183463

llvm-svn: 183461

llvm-svn: 183458

Jeffrey Yasskin volunteered to benchmark the vectorizer on -O2 or -Os when compiling chrome. This patch adds a new flag to enable vectorization on all levels and not only on -O3. It should go away once we make a decision.

llvm-svn: 183456

llvm-svn: 183454

Breaks linux build bots (I thought the problem was something else).

llvm-svn: 183447

Seems we emit the parameter ordering number (spuriously named 'arg
number') in the debug info, so there's no need to search through the
variable list to figure out the parameter ordering. This implementation
does 'always' do the work, even in non-optimized debug info (the
previous implementation checked the existence of the 'variables' list on
the subprogram which is only present in optimized builds).

No intended functionality change.

llvm-svn: 183446

Reapply 183270.

llvm-svn: 183445

Reapply 183269.

llvm-svn: 183441

llvm-svn: 183439

Reapply 183268.

llvm-svn: 183438

Reapply 183267.

llvm-svn: 183436

Add more InstRW mappings.

Reapply 183266.

llvm-svn: 183435

Reapply 183265.

llvm-svn: 183432

Reapply 183264.

llvm-svn: 183430

Reapply 183263.

llvm-svn: 183428

Reapply 183262.

llvm-svn: 183427

Reapply 183261.

llvm-svn: 183425

from the LC_DATA_IN_CODE load command.  And when disassembling print
the data in code formatted for the kind of data it and not disassemble those
bytes.

I added the format specific functionality to the derived class MachOObjectFile
since these tables only appears in Mach-O object files. This is my first
attempt to modify the libObject stuff so if folks have better suggestions
how to fit this in or suggestions on the implementation please let me know.

rdar://11791371

llvm-svn: 183424

Reapply of 183260.

llvm-svn: 183423

This reverts commit 183328. It caused pr16244 and broke the bots.

llvm-svn: 183422

Reapply of 183259.

llvm-svn: 183421

Spotted by Benjamin Kramer.

llvm-svn: 183413