maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
148,518 Commits 23 Branches 0 Tags 2.2 GiB
Commit Graph

12 Commits

Author SHA1 Message Date
Chandler Carruth 802d755533 Sort includes for all of the .h files under the 'lib' tree. These were 
missed in the first pass because the script didn't yet handle include
guards.

Note that the script is now able to handle all of these headers without
manual edits. =]

llvm-svn: 169224
 2012-12-04 07:12:27 +00:00
Devang Patel b7ae3ccb84 Do not lose debug info of an inlined function argument even if the argument is only used through GEPs. 
This time with a fix that avoids using invalidated DenseMap iterator.

llvm-svn: 125984
 2011-02-18 22:43:42 +00:00
Cameron Zwarich 0a1a36dc46 Roll out r125794 to help diagnose the llvm-gcc-i386-linux-selfhost failure. 
llvm-svn: 125830
 2011-02-18 04:58:10 +00:00
Devang Patel f922a431ee Do not lose debug info of an inlined function argument even if the argument is only used through GEPs. 
llvm-svn: 125794
 2011-02-17 23:33:27 +00:00
Devang Patel efc6b16e4b Provide an interface to transfer SDDbgValue from one SDNode to another. 
llvm-svn: 124245
 2011-01-25 23:27:42 +00:00
Michael J. Spencer 447762da85 Merge System into Support. 
llvm-svn: 120298
 2010-11-29 18:16:10 +00:00
Dan Gohman bcaf681cde Add const qualifiers to CodeGen's use of LLVM IR constructs. 
llvm-svn: 101334
 2010-04-15 01:51:59 +00:00
Benjamin Kramer cc034c7879 Fix anachronism. 
llvm-svn: 100225
 2010-04-02 20:47:05 +00:00
Chris Lattner 47857a9176 fix the llvm-x86_64-linux buildbot. 
llvm-svn: 100223
 2010-04-02 20:36:25 +00:00
Evan Cheng 7f0b16a206 Make sure SDDbgValue.Invalid is initialized to false by all the constructors. 
llvm-svn: 99487
 2010-03-25 05:50:26 +00:00
Evan Cheng 563fe3cc12 Change how dbg_value sdnodes are converted into machine instructions. Their placement should be determined by the relative order of incoming llvm instructions. The scheduler will now use the SDNode ordering information to determine where to insert them. A dbg_value instruction is inserted after the instruction with the last highest source order and before the instruction with the next highest source order. It will optimize the placement by inserting right after the instruction that produces the value if they have consecutive order numbers. 
Here is a theoretical example that illustrates why the placement is important.

tmp1 = 
store tmp1 -> x
...
tmp2 = add ...
...
call
...
store tmp2 -> x

Now mem2reg comes along:

tmp1 = 
dbg_value (tmp1 -> x)
...
tmp2 = add ...
...
call
...
dbg_value (tmp2 -> x)

When the debugger examine the value of x after the add instruction but before the call, it should have the value of tmp1.

Furthermore, for dbg_value's that reference constants, they should not be emitted at the beginning of the block (since they do not have "producers").

This patch also cleans up how SDISel manages DbgValue nodes. It allow a SDNode to be referenced by multiple SDDbgValue nodes. When a SDNode is deleted, it uses the information to find the SDDbgValues and invalidate them. They are not deleted until the corresponding SelectionDAG is destroyed.

llvm-svn: 99469
 2010-03-25 01:38:16 +00:00
Evan Cheng 00fd0b6749 Rename SDDbgValue.h to SDNodeDbgValue.h for consistency. 
llvm-svn: 98513
 2010-03-14 19:56:39 +00:00