Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Test case updates for explicit type parameter to the gep operator | David Blaikie | 2015-03-13 | 1 | -2/+2 |
| | | | | llvm-svn: 232187 | ||||
* | fix an unintended behavior change in the type system rewrite, which caused ↵ | Chris Lattner | 2011-07-12 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | us to compile stuff like this: typedef struct { int x, y, z; } foo_t; foo_t g; into: %"struct.<anonymous>" = type { i32, i32, i32 } we now get: %struct.foo_t = type { i32, i32, i32 } This doesn't change the behavior of the compiler, but makes the IR much easier to read. llvm-svn: 134969 | ||||
* | clang side to match the LLVM IR type system rewrite patch. | Chris Lattner | 2011-07-09 | 1 | -2/+2 |
| | | | | llvm-svn: 134831 | ||||
* | stop looking for #uses comments. | Chris Lattner | 2010-09-02 | 1 | -2/+2 |
| | | | | llvm-svn: 112898 | ||||
* | Correctly align large arrays in x86-64. This fixes PR5599. | Rafael Espindola | 2010-06-04 | 1 | -2/+2 |
| | | | | llvm-svn: 105500 | ||||
* | Evaluate: Fix a subtle bug in the pointer evaluator in which we would do an | Daniel Dunbar | 2010-03-20 | 1 | -0/+8 |
expression computation in the wrong bit-width, and end up generating a totally bogus array reference (_g0+8589934546). - This showed up on Prolangs/cdecl. llvm-svn: 99042 |