| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | SAFE_HEAP: Avoid annotating any function reachable from start function (#4463) | Sam Clegg | 2022-01-19 | 1 | -1/+6 |
| | | | | | | | Since https://reviews.llvm.org/D117412 landed it has causes a bunch of SAFE_HEAP tests in emscripten to start failing, because `__wasm_apply_data_relocs` can now sometimes be called from with `__wasm_init_memory` as opposed to directly from the start function. | ||||
| * | SafeHeap: Avoid instrumenting functions directly called from the "start" (#4439) | Sam Clegg | 2022-01-10 | 1 | -2/+7 |
| | | |||||
| * | Don't apply SafeHeap to wasm start function (#3424) | Sam Clegg | 2020-12-04 | 1 | -0/+11 |
| In relocable code (MAIN/SIDE modules) we use the start function to run `__wasm_init_memory` which loads the data segments into place. We can't call get_sbkr pointer during that function because the sbrk pointer itself lives in static data segment. | |||||
 |
index : forks/binaryen.git | |
| summaryrefslogtreecommitdiff |