llvm-svn: 58728

  "getOrInsertFunction" in that it either adds a new declaration of the global
  and returns it, or returns the current one -- optionally casting it to the
  correct type.
- Use the new getOrInsertGlobal in the stack protector code.
- Use "splitBasicBlock" in the stack protector code.

llvm-svn: 58727

First pass at checking for the creation of a new join point when doing pre-alloc splitting.  This is not turned on yet.

llvm-svn: 58726

llvm-svn: 58725

- Use enums instead of magic numbers.

- Rework algorithm to use the bytes size from the target to determine when to
  emit stack protectors.

- Get rid of "propolice" in any comments.

- Renamed an option to its expanded form.

- Other miscellanenous changes.

More changes will come after this.

llvm-svn: 58723

llvm-svn: 58722

llvm-svn: 58721

llvm-svn: 58719

huge performance regression in something we care
about.  This may not be final fix.

llvm-svn: 58718

llvm-svn: 58717

llvm-svn: 58714

llvm-svn: 58712

"Type has virtual functions but non-virtual destructor"
warnings.

llvm-svn: 58710

llvm-svn: 58709

llvm-svn: 58708

llvm-svn: 58707

SELECT_CC.

llvm-svn: 58706

be considerably simplified.

llvm-svn: 58703

llvm-svn: 58702

llvm-svn: 58701

llvm-svn: 58697

llvm-svn: 58696

llvm-svn: 58694

llvm-svn: 58693

llvm-svn: 58690

For some targets, it's not possible to place GVs in the same memory buffer as the MachineCodeEmitter allocated memory. Code and data has different read / write / execution privilege requirements.

This is a short term workaround. The current solution is for the JIT memory manager to manage code and data memory separately.

llvm-svn: 58688

friendlier to non-Unixes that happen to have perl. Patch from Sascha Othman!

llvm-svn: 58687

llvm-svn: 58684

llvm-svn: 58683

llvm-svn: 58682

tools/llc/CMakeLists.txt.

llvm-svn: 58678

Linux/x86-64.

llvm-svn: 58677

llvm-svn: 58676

* The prologue is modified to read the __stack_chk_guard global and insert it
  onto the stack.

* The epilogue is modified to read the stored guard from the stack and compare
  it to the original __stack_chk_guard value. If they differ, then the
  __stack_chk_fail() function is called.

* The stack protector needs to be first on the stack (after the parameters) to
  catch any stack-smashing activities.

Front-end support will follow after a round of beta testing.

llvm-svn: 58673

llvm-svn: 58671

have its node id set. The new and and shift nodes are the nodes that need
the IDs. This fixes PR2982.

llvm-svn: 58655

llvm-svn: 58653

llvm-svn: 58651

llvm-svn: 58650

llvm-svn: 58644