| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | HHVM calling conventions. | Maksim Panchenko | 2015-09-29 | 1 | -0/+7 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | HHVM calling convention, hhvmcc, is used by HHVM JIT for functions in translated cache. We currently support LLVM back end to generate code for X86-64 and may support other architectures in the future. In HHVM calling convention any GP register could be used to pass and return values, with the exception of R12 which is reserved for thread-local area and is callee-saved. Other than R12, we always pass RBX and RBP as args, which are our virtual machine's stack pointer and frame pointer respectively. When we enter translation cache via hhvmcc function, we expect the stack to be aligned at 16 bytes, i.e. skewed by 8 bytes as opposed to standard ABI alignment. This affects stack object alignment and stack adjustments for function calls. One extra calling convention, hhvm_ccc, is used to call C++ helpers from HHVM's translation cache. It is almost identical to standard C calling convention with an exception of first argument which is passed in RBP (before we use RDI, RSI, etc.) Differential Revision: http://reviews.llvm.org/D12681 llvm-svn: 248832 | ||||
| * | Move the personality function from LandingPadInst to Function | David Majnemer | 2015-06-17 | 1 | -4/+4 |
| | | | | | | | | | | | | | | | | | | | | The personality routine currently lives in the LandingPadInst. This isn't desirable because: - All LandingPadInsts in the same function must have the same personality routine. This means that each LandingPadInst beyond the first has an operand which produces no additional information. - There is ongoing work to introduce EH IR constructs other than LandingPadInst. Moving the personality routine off of any one particular Instruction and onto the parent function seems a lot better than have N different places a personality function can sneak onto an exceptional function. Differential Revision: http://reviews.llvm.org/D10429 llvm-svn: 239940 | ||||
| * | Parse 'ghccc' in .ll files as the GHC convention (cc 10) | Reid Kleckner | 2014-12-01 | 1 | -0/+7 |
| | | | | | | | | Previously we just used "cc 10" in the .ll files, but that isn't very human readable. llvm-svn: 223076 | ||||
| * | Update tests to the newest EH syntax. | Bill Wendling | 2011-08-25 | 1 | -13/+18 |
| | | | | | llvm-svn: 138541 | ||||
| * | Remove llvm-upgrade and update tests. | Tanya Lattner | 2008-03-01 | 1 | -29/+32 |
| | | | | | llvm-svn: 47784 | ||||
| * | Use the llvm-upgrade program to upgrade llvm assembly. | Reid Spencer | 2006-12-02 | 1 | -1/+1 |
| | | | | | llvm-svn: 32115 | ||||
| * | new testcase for csretcc | Chris Lattner | 2006-05-19 | 1 | -0/+5 |
| | | | | | llvm-svn: 28413 | ||||
| * | new testcase | Chris Lattner | 2005-05-06 | 1 | -0/+42 |
| llvm-svn: 21750 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|