- Nov 18, 2008
-
-
Bill Wendling authored
- Use less indentation in coding. - Shorten description. - Update comments. - Move code around llvm-svn: 59496
-
- Nov 13, 2008
-
-
Bill Wendling authored
llvm-svn: 59202
-
- Nov 11, 2008
-
-
Bill Wendling authored
llvm-svn: 59008
-
- Nov 10, 2008
-
-
Bill Wendling authored
basic blocks. - Minor code clean-up. llvm-svn: 59002
-
- Nov 07, 2008
-
-
Bill Wendling authored
LLVM IR code and not in the selection DAG ISel. This is a cleaner solution. - Fix the heuristic for determining if protectors are necessary. The previous one wasn't checking the proper type size. llvm-svn: 58824
-
Bill Wendling authored
llvm-svn: 58823
-
Bill Wendling authored
llvm-svn: 58822
-
- Nov 06, 2008
-
-
Bill Wendling authored
in it, then emit stack protectors. llvm-svn: 58819
-
Bill Wendling authored
- Get rid of "HasStackProtector" in MachineFrameInfo. - Modify intrinsics to tell which are doing what with memory. llvm-svn: 58799
-
Bill Wendling authored
"alloca". llvm-svn: 58792
-
Bill Wendling authored
- stackprotector_prologue creates a stack object and stores the guard there. - stackprotector_epilogue reads the stack guard from the stack position created by stackprotector_prologue. - The PrologEpilogInserter was changed to make sure that the stack guard is first on the stack frame. llvm-svn: 58791
-
- Nov 05, 2008
-
-
Bill Wendling authored
llvm-svn: 58741
-
Bill Wendling authored
llvm-svn: 58740
-
Bill Wendling authored
llvm-svn: 58739
-
Bill Wendling authored
isn't going to be generated. llvm-svn: 58734
-
- Nov 04, 2008
-
-
Bill Wendling authored
llvm-svn: 58728
-
Bill Wendling authored
"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
-
Bill Wendling authored
- 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
-
Bill Wendling authored
* 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
-