| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | I had meant to locally revert this test. | John McCall | 2011-09-21 | 1 | -1/+1 |
| | | | | | llvm-svn: 140243 | ||||
| * | ANSI C requires that a call to an unprototyped function type succeed | John McCall | 2011-09-21 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | if the definition has a non-variadic prototype with compatible parameters. Therefore, the default rule for such calls must be to use a non-variadic convention. Achieve this by casting the callee to the function type with which it is required to be compatible, unless the target specifically opts out and insists that unprototyped calls should use the variadic rules. The only case of that I'm aware of is the x86-64 convention, which passes arguments the same way in both cases but also sets a small amount of extra information; here we seek to maintain compatibility with GCC, which does set this when calling an unprototyped function. Addresses PR10810 and PR10713. llvm-svn: 140241 | ||||
| * | Introduce __builtin_expect() intrinsic support. | Jakub Staszak | 2011-07-08 | 1 | -0/+26 |
| | | | | | llvm-svn: 134761 | ||||
| * | Ir-gen the side-effect(s) when __builtin_expect is | Fariborz Jahanian | 2011-04-25 | 1 | -1/+11 |
| | | | | | | | constant-folded. // rdar://9330105 llvm-svn: 130163 | ||||
| * | 2nd argument of __builtin_expect must be evaluated | Fariborz Jahanian | 2010-07-26 | 1 | -0/+11 |
| if it hs side-effect to matchgcc's behaviour. Addresses radar 8172109. llvm-svn: 109467 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|