- Jan 05, 2009
-
-
Dan Gohman authored
- After GlobalAssign, emit addrspace before global/constant, to follow the new syntax. - Eliminate "type void", which is now invalid. - Fix invalid liblists like [, "foo"]. - Tweak whitespace in a few places. llvm-svn: 61706
-
Gabor Greif authored
llvm-svn: 61703
-
Bob Wilson authored
llvm-svn: 61702
-
Gabor Greif authored
* some picky <g> compilers get insulted by const-incorrectness * respect 80-char limit llvm-svn: 61701
-
Douglas Gregor authored
llvm-svn: 61700
-
Evan Cheng authored
llvm-svn: 61699
-
Gabor Greif authored
llvm-svn: 61695
-
Gabor Greif authored
This means that we have to include an additional header. This patch should be functionally equivalent. I cannot outrule any performance degradation, though I do not expect any. llvm-svn: 61694
-
Duncan Sands authored
fails, like it is right now. llvm-svn: 61690
-
Torok Edwin authored
llvm-svn: 61688
-
Evan Cheng authored
llvm-svn: 61686
-
Chris Lattner authored
llvm-svn: 61685
-
Chris Lattner authored
llvm-as: crash08.ll:3:15: invalid operand type for instruction "qp" = sdiv fp128 0x1, %30 ^ llvm-svn: 61684
-
Chris Lattner authored
llvm-as: crash07.ll:2:32: va_arg requires operand with first class type %y = va_arg [52 x <{}>] %43, double (...) sspreq ^ llvm-svn: 61683
-
Chris Lattner authored
llvm-svn: 61682
-
Chris Lattner authored
diagnostics: llvm-as: crash05.ll:1:14: invalid type for null constant global label zeroinitializer addrspace (75), section "c" ^ llvm-as: crash06.ll:2:14: invalid type for null constant udiv label zeroinitializer, @0 ^ llvm-svn: 61681
-
Chris Lattner authored
just be removed. However, this fixes PR3281:crash04.ll, diagnosing it with: lvm-as: crash04.ll:2:13: vfcmp requires vector floating point operands vfcmp uno double* undef, undef ^ llvm-svn: 61680
-
Chris Lattner authored
llvm-as: crash02.ll:1:62: invalid function return type declare { <{ <{}>, void ([1898 x { void ()* }], opaque, ...) (), fp128 * }>, opaque } @t () ^ llvm-svn: 61679
-
Chris Lattner authored
llvm-as: crash01.ll:1:9: invalid function return type declare opaque @t() ^ llvm-svn: 61678
-
Chris Lattner authored
llvm-svn: 61677
-
Chris Lattner authored
diagnose attempts to initialize non-empty arrays with them. This produces: llvm-as: accepted02.ll:1:28: invalid empty array initializer @"o" = global [5 x double] [] ^ llvm-as: accepted00.ll:1:32: invalid empty array initializer @"za" = thread_local global {} [] ^ [ llvm-svn: 61676
-
Chris Lattner authored
@t = global i8 0, align 3 ^ llvm-svn: 61675
-
Dan Gohman authored
SingleSource/UnitTests/2007-04-25-weak.c in JIT mode. The test now passes on systems which are able to produce a correct reference output to compare with. llvm-svn: 61674
-
Scott Michel authored
- Teach SPU64InstrInfo.td about the remaining signed comparisons, update tests accordingly. llvm-svn: 61672
-
Chris Lattner authored
isn't worth the complexity and the code already does a ton of lookahead. llvm-svn: 61671
-
Dan Gohman authored
llvm-svn: 61670
-
Dan Gohman authored
llvm-svn: 61669
-
Chris Lattner authored
llvm-svn: 61668
-
Chris Lattner authored
early exit for C and avoid template lookup for C. llvm-svn: 61667
-
Chris Lattner authored
not in backtracking mode. This was just using the wrong predicate. llvm-svn: 61666
-
Scott Michel authored
- Add an 8-bit operation test, which doesn't do much at this point. llvm-svn: 61665
-
Scott Michel authored
- Fix (brcond (setq ...)) bug, where BRNZ should have been used vice BRZ. - Kill unused/unnecessary nodes in SPUNodes.td - Beef out the i64operations.c test harness to use a lot of unaligned loads, test loops and LLVM loop/basic block optimizations; run the test harness successfully on real Cell hardware. llvm-svn: 61664
-
Anders Carlsson authored
llvm-svn: 61663
-
Chris Lattner authored
only be called when they might be needed now, so make them assert that their current token is :: or identifier. llvm-svn: 61662
-
Anders Carlsson authored
llvm-svn: 61661
-
Chris Lattner authored
llvm-svn: 61660
-
Chris Lattner authored
verified to be simple type specifiers, so there is no need for it to call TryAnnotateTypeOrScopeToken. Make MaybeParseCXXScopeSpecifier reject ::new and ::delete with a hard error now that it may never be transitively called in a context where these are legal. This allows me to start disentangling things more. llvm-svn: 61659
-
Nick Lewycky authored
Finalization occurs after all the FunctionPasses in the group have run, which is clearly not what we want. This also means that we have to make sure that we apply the right param attributes when creating a new function. Also, add a missed optimization: strdup and strndup. NoCapture and NoAlias return! llvm-svn: 61658
-
Chris Lattner authored
applicable cases in ParseDeclarationSpecifiers. llvm-svn: 61657
-
Chris Lattner authored
that isn't doing what is desired. It was annotating the current token not the 'next' token. This code should be fixed. llvm-svn: 61656
-