summaryrefslogtreecommitdiffstats
path: root/clang/test/CodeGen/builtin-expect.c
Commit message (Collapse)AuthorAgeFilesLines
* Add testcase from bug 41079Matt Arsenault2019-03-171-0/+17
| | | | llvm-svn: 356354
* Make '-disable-llvm-optzns' an alias for '-disable-llvm-passes'.Chandler Carruth2016-12-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Much to my surprise, '-disable-llvm-optzns' which I thought was the magical flag I wanted to get at the raw LLVM IR coming out of Clang deosn't do that. It still runs some passes over the IR. I don't want that, I really want the *raw* IR coming out of Clang and I strongly suspect everyone else using it is in the same camp. There is actually a flag that does what I want that I didn't know about called '-disable-llvm-passes'. I suspect many others don't know about it either. It both does what I want and is much simpler. This removes the confusing version and makes that spelling of the flag an alias for '-disable-llvm-passes'. I've also moved everything in Clang to use the 'passes' spelling as it seems both more accurate (*all* LLVM passes are disabled, not just optimizations) and much easier to remember and spell correctly. This is part of simplifying how Clang drives LLVM to make it cleaner to wire up to the new pass manager. Differential Revision: https://reviews.llvm.org/D28047 llvm-svn: 290392
* [builtin_expect] tighten checks, add test, add commentsSanjay Patel2016-04-191-25/+50
| | | | llvm-svn: 266788
* [opaque pointer types] Explicit non-pointer type for call expressionsDavid Blaikie2015-04-161-2/+2
| | | | | | (migration for recent LLVM change to textual IR for calls) llvm-svn: 235147
* Don't generate llvm.expect intrinsics with -O0.Pete Cooper2015-01-261-4/+12
| | | | | | | | | | The backend won't run LowerExpect on -O0. In a debug LTO build, this results in llvm.expect intrinsics being in the LTO IR which doesn't know how to optimize them. Thanks to Chandler for the suggestion and review. Differential revision: http://reviews.llvm.org/D7183 llvm-svn: 227135
* I had meant to locally revert this test.John McCall2011-09-211-1/+1
| | | | llvm-svn: 140243
* ANSI C requires that a call to an unprototyped function type succeedJohn McCall2011-09-211-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 Staszak2011-07-081-0/+26
| | | | llvm-svn: 134761
* Ir-gen the side-effect(s) when __builtin_expect isFariborz Jahanian2011-04-251-1/+11
| | | | | | constant-folded. // rdar://9330105 llvm-svn: 130163
* 2nd argument of __builtin_expect must be evaluatedFariborz Jahanian2010-07-261-0/+11
if it hs side-effect to matchgcc's behaviour. Addresses radar 8172109. llvm-svn: 109467
OpenPOWER on IntegriCloud