isn't going to be generated.

llvm-svn: 58734

a specialized pass that it not likely to be generally useful.

llvm-svn: 58732

fix memory leak in pass manager when adding an analysis pass that already existed. as pass manager takes ownership of the added passes, it has to delete the pass if it isnt added to the pass list
tweak the opt tool so that it doesnt access a Pass after the ownership was taken by the pass manager

llvm-svn: 58730

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

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: 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

llvm-svn: 58684

llvm-svn: 58683

llvm-svn: 58682

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

llvm-svn: 58643

work correctly, and bring over a late change to ppcf128
SetCC handling.

llvm-svn: 58642

sized integers like i129, and also reduce the number
of assumptions made about how vaarg is implemented.
This still doesn't work correctly for small integers
like (eg) i1 on x86, since x86 passes each of them
(essentially an i8) in a 4 byte stack slot, so the
pointer needs to be advanced by 4 bytes not by 1 byte
as now.  But this is no longer a LegalizeTypes problem
(it was also wrong in LT before): it is a bug in the
operation expansion in LegalizeDAG: now LegalizeTypes
turns an i1 vaarg into an i8 vaarg which would work
fine if only the i8 vaarg was turned into correct code
later.

llvm-svn: 58635

to avoid overload ambiguities. This fixes build errors introduced
by r58623.

llvm-svn: 58632

llvm-svn: 58631