| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Move getInitialFrameState from TargetFrameInfo to MCAsmInfo (suggestions for | Evan Cheng | 2011-07-18 | 1 | -1/+0 |
| | | | | | | | better location welcome). llvm-svn: 135438 | ||||
| * | Emit the handler's data area. For GCC-style exceptions under Win64, the | Charles Davis | 2011-05-30 | 1 | -0/+21 |
| | | | | | | | | handler's data area starts with a 4-byte reference to the personality function, followed by the DWARF LSDA. llvm-svn: 132302 | ||||
| * | When generating against the Win64 EH scheme, set the handler to the GCC-specific | Charles Davis | 2011-05-29 | 1 | -0/+7 |
| | | | | | | | | | | | | | | | | | handler. At this moment, only GCC-style exceptions are supported. Other kinds of exceptions, including "traditional" SEH and Microsoft Visual C++ exceptions, need more work--and an compiler exception model that isn't specific to GCC-style exceptions! In particular, I imagine that it would be possible to mix "traditional" SEH with GCC-style EH or Microsoft C++ EH. Currently LLVM has no way (beyond some target-specific defaults and whole-module compiler switches) of knowing which scheme to use when. llvm-svn: 132283 | ||||
| * | When generating code for Win64 EH, emit StartProc and EndProc directives. | Charles Davis | 2011-05-28 | 1 | -0/+26 |
| | | | | | llvm-svn: 132250 | ||||
| * | Stub out support for Win64-style exceptions. Note that this is merely using | Charles Davis | 2011-05-27 | 1 | -0/+62 |
| the Win64 EH mechanism to implement GCC-style exceptions. LLVM supports hardly anything else at this point! llvm-svn: 132234 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|