- Jul 26, 2009
-
-
Daniel Dunbar authored
llvm-svn: 77148
-
Daniel Dunbar authored
llvm-svn: 77145
-
Daniel Dunbar authored
Also, change MDString to use a StringRef. llvm-svn: 77098
-
- Jul 25, 2009
-
-
Daniel Dunbar authored
- The only meat here is in Value.{h,cpp} the rest is essential 'const std::string &' -> 'const Twine &'. llvm-svn: 77048
-
Eric Christopher authored
llvm-svn: 77045
-
Eric Christopher authored
llvm-svn: 77044
-
Dan Gohman authored
llvm-svn: 77039
-
Dan Gohman authored
llvm-svn: 77033
-
Dan Gohman authored
getAnalysisIfAvailable<TargetData>(). llvm-svn: 77028
-
Daniel Dunbar authored
- Some clients which used DOUT have moved to DEBUG. We are deprecating the "magic" DOUT behavior which avoided calling printing functions when the statement was disabled. In addition to being unnecessary magic, it had the downside of leaving code in -Asserts builds, and of hiding potentially unnecessary computations. llvm-svn: 77019
-
Owen Anderson authored
Revert the ConstantInt constructors back to their 2.5 forms where possible, thanks to contexts-on-types. More to come. llvm-svn: 77011
-
Dan Gohman authored
llvm-svn: 77009
-
- Jul 24, 2009
-
-
Dan Gohman authored
llvm-svn: 76988
-
Dan Gohman authored
instead of getAnalysis<TargetData>(). llvm-svn: 76982
-
Daniel Dunbar authored
LiveInterval, etc to raw_ostream. llvm-svn: 76965
-
Daniel Dunbar authored
llvm-svn: 76962
-
- Jul 23, 2009
-
-
Daniel Dunbar authored
- Yay for '-'s and simplifications! - I kept StringMap::GetOrCreateValue for compatibility purposes, this can eventually go away. Likewise the StringMapEntry Create functions still follow the old style. - NIFC. llvm-svn: 76888
-
Chris Lattner authored
simplify it. llvm-svn: 76866
-
Chris Lattner authored
also apply to vectors. This allows us to compile this: #include <emmintrin.h> __m128i a(__m128 a, __m128 b) { return a==a & b==b; } __m128i b(__m128 a, __m128 b) { return a!=a | b!=b; } to: _a: cmpordps %xmm1, %xmm0 ret _b: cmpunordps %xmm1, %xmm0 ret with clang instead of to a ton of horrible code. llvm-svn: 76863
-
Chris Lattner authored
no functionality change. llvm-svn: 76859
-
- Jul 22, 2009
-
-
Daniel Dunbar authored
llvm-svn: 76782
-
Eli Friedman authored
functions with a single use; eliminating the single use may eliminate the function from the current module, but usually doesn't eliminate it from the final program. llvm-svn: 76730
-
Owen Anderson authored
llvm-svn: 76702
-
Dan Gohman authored
getAnalysisIfAvailable<TargetData>. llvm-svn: 76676
-
- Jul 21, 2009
-
-
Owen Anderson authored
llvm-svn: 76598
-
Ted Kremenek authored
llvm-svn: 76595
-
Owen Anderson authored
llvm-svn: 76533
-
- Jul 20, 2009
-
-
Chris Lattner authored
llvm-svn: 76442
-
Dan Gohman authored
Getelementptrs that are defined to wrap are virtually useless to optimization, and getelementptrs that are undefined on any kind of overflow are too restrictive -- it's difficult to ensure that all intermediate addresses are within bounds. I'm going to take a different approach. Remove a few optimizations that depended on this flag. llvm-svn: 76437
-
Chris Lattner authored
doesn't cause ".no_dead_strip" to be emitted on darwin. llvm-svn: 76399
-
Bill Wendling authored
"private" symbols which the assember shouldn't strip, but which the linker may remove after evaluation. This is mostly useful for Objective-C metadata. This is plumbing, so we don't have a use of it yet. More to come, etc. llvm-svn: 76385
-
- Jul 19, 2009
-
-
Eli Friedman authored
insertelement/extractelement. I'm not entirely sure this is precisely what we want to do: should we prefer bitcast(insertelement) or insertelement(bitcast)? Similarly. should we prefer extractelement(bitcast) or bitcast(extractelement)? llvm-svn: 76345
-
- Jul 18, 2009
-
-
Eli Friedman authored
way (bitcast -> insert/extractelement). llvm-svn: 76325
-
Chris Lattner authored
llvm-svn: 76324
-
Eli Friedman authored
sign bit set. llvm-svn: 76304
-
Eli Friedman authored
llvm-svn: 76302
-
Eli Friedman authored
llvm-svn: 76301
-
Eli Friedman authored
bitcasts. It would also be possible to canonicalize the other way; does anyone have a preference? llvm-svn: 76300
-
Eli Friedman authored
where int is 32 bits. llvm-svn: 76293
-
Nick Lewycky authored
all values belonging to the intersection will belong to the resulting range. The former was inconsistent about that point (either way is fine, just pick one.) This is part of PR4545. llvm-svn: 76289
-