- Jan 23, 2009
-
-
Devang Patel authored
DW_AT_APPLE_optimized flag is set when a compile_unit is optimized. The debugger takes advantage of this information some way. DW_AT_APPLE_flags encodes command line options when certain env. variable is set. This is used by build engineers to track various gcc command lines used by by a project, irrespective of whether the project used makefile, Xcode or something else. llvm-gcc patch is next. llvm-svn: 62888
-
Chris Lattner authored
llvm-svn: 62887
-
Devang Patel authored
llvm-svn: 62883
-
Gabor Greif authored
llvm-svn: 62877
-
Gabor Greif authored
There is now a direct way from value-use-iterator to incoming block in PHINode's API. This way we avoid the iterator->index->iterator trip, and especially the costly getOperandNo() invocation. Additionally there is now an assertion that the iterator really refers to one of the PHI's Uses. llvm-svn: 62869
-
Nate Begeman authored
Add support for deleting a module provider from a JIT in such a way that it does not cause the owned module to be fully materialized. llvm-svn: 62864
-
Devang Patel authored
llvm-svn: 62861
-
Dan Gohman authored
testcase from PR3376, and in fact is sufficient to completely avoid the problem in that testcase. There's an underlying problem though; TLI.isOperationLegal considers Custom to be Legal, which might be ok in some cases, but that's what DAGCombiner is using in many places to test if something is legal when LegalOperations is true. When DAGCombiner is running after legalize, this isn't sufficient. I'll address this in a separate commit. llvm-svn: 62860
-
Duncan Sands authored
llvm-top. By Michael Schuerig, with some small tweaks to make the "don't configure if already configured" logic work. llvm-svn: 62842
-
Chris Lattner authored
With this, sqlite3 now passes. llvm-svn: 62839
-
Chris Lattner authored
This avoids using a dangling pointer. Reset NumSortedEntries after restoring Cache to avoid extraneous sorts. This fixes the reduced sqlite3 testcase, but apparently not the whole app. llvm-svn: 62838
-
Evan Cheng authored
Only check if coalescing is worthwhile when the result is targeting a more restrictive register class. llvm-svn: 62837
-
Evan Cheng authored
llvm-svn: 62836
-
Owen Anderson authored
going to be re-spilled again. This also helps performance. Pre-alloc-splitting now seems to be an overall win on SPEC. llvm-svn: 62834
-
Evan Cheng authored
llvm-svn: 62832
-
Devang Patel authored
llvm-svn: 62828
-
Devang Patel authored
llvm-svn: 62827
-
Chris Lattner authored
when there are multiple iterations of the loop. This fixes PR3375. llvm-svn: 62822
-
Owen Anderson authored
llvm-svn: 62821
-
Chris Lattner authored
compatibility with VC++. Patch by Max Burke! llvm-svn: 62813
-
Steve Naroff authored
Handful of fixes to the VC project files. llvm-svn: 62807
-
- Jan 22, 2009
-
-
Bob Wilson authored
to "C ^ 1" is only valid when C is known to be either 0 or 1. Most of the similar foldings in this function only handle "i1" types, but this one appears intentionally written to handle larger integer types. If C has an integer type larger than "i1", this needs to check if the high bits of a boolean are known to be zero. I also changed the comment to describe this folding as "C ^ 1" instead of "~C", since that is what the code does and since the latter would only be valid for "i1" types. The good news is that most LLVM targets use TargetLowering::ZeroOrOneBooleanContent so this change will not disable the optimization; the bad news is that I've been unable to come up with a testcase to demonstrate the problem. I have also removed a "FIXME" comment for folding "select C, X, 0" to "C & X", since the code looks correct to me. It could be made more aggressive by not limiting the type to "i1", but that would then require checking for TargetLowering::ZeroOrNegativeOneBooleanContent. Similar changes could be done for the other SELECT foldings, but it was decided to be not worth the trouble and complexity (see e.g., r44663). llvm-svn: 62790
-
Dan Gohman authored
Simplify x+0 to x in unsafe-fp-math mode. This avoids a bunch of redundant work in many cases, because in unsafe-fp-math mode, ISD::FADD with a constant is considered free to negate, so the DAGCombiner often negates x+0 to -0-x thinking it's free, when in reality the end result is -x, which is more expensive than x. Also, combine x*0 to 0. This fixes PR3374. llvm-svn: 62789
-
Gabor Greif authored
llvm-svn: 62788
-
Tanya Lattner authored
llvm-svn: 62778
-
Tanya Lattner authored
llvm-svn: 62777
-
Chris Lattner authored
llvm-svn: 62776
-
Devang Patel authored
llvm-svn: 62770
-
Bob Wilson authored
corresponding to the "not" and "vnot" PatFrags. Use the new method in some places where it seems appropriate. llvm-svn: 62768
-
Duncan Sands authored
by Gabor. llvm-svn: 62765
-
Duncan Sands authored
llvm-svn: 62764
-
Sanjiv Gupta authored
llvm-svn: 62763
-
Evan Cheng authored
Eliminate a couple of fields from TargetRegisterClass: SubRegClasses and SuperRegClasses. These are not necessary. Also eliminate getSubRegisterRegClass and getSuperRegisterRegClass. These are slow and their results can change if register file names change. Just use TargetLowering::getRegClassFor() to get the right TargetRegisterClass instead. llvm-svn: 62762
-
Chris Lattner authored
llvm-svn: 62761
-
Chris Lattner authored
llvm-svn: 62760
-
Chris Lattner authored
llvm-svn: 62758
-
Chris Lattner authored
analyses could be run without the caches properly sorted. This can fix all sorts of weirdness. Many thanks to Bill for coming up with the 'issorted' verification idea. llvm-svn: 62757
-
Tanya Lattner authored
Regenerate configure (last regen was with the wrong version). llvm-svn: 62751
-
Chris Lattner authored
Patch by Robert Zeh! llvm-svn: 62750
-
Mike Stump authored
order-only dependancies for installation directories. llvm-svn: 62746
-