en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#122b0220 [WebAssembly] Remove datalayout strings from llc testsThe data layout strings do not have any effect on llc tests and will becomemisleadingly out of date as we continue to update the canonical data layout, soremove them from the tests.Differential Revision: https://reviews.llvm.org/D105842 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Wed, 14 Jul 2021 18:17:08 +0000 Thomas Lively <tlively@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#c390621a [WebAssembly] Fix fixEndsAtEndOfFunction for delegateBackground:CFGStackify's [[ https://github.com/llvm/llvm-project/blob/398f25340000f26d648ebbc7eae9dc401ffc7d5f/llvm/lib/Target/WebAssembly/WebAssemblyCFGStackify.cpp#L1481-L1540 | fixEndsAtEndOfFunction ]] fixes block/loop/try's returntype when the end of function is unreachable and the function returntype is not void. So if a function returns i32 and `block`-`end` wraps thewhole function, i.e., the `block`'s `end` is the last instruction of thefunction, the `block`'s return type should be i32 too:```block i32 ...endend_function```If there are consecutive `end`s, this signature has to be propagate tothose blocks too, like:```block i32 ... block i32 ... endendend_function```This applies to `try`-`end` too:```try i32 ...catch ...endend_function```In case of `try`, we not only follow consecutive `end`s but also follow`catch`, because for the type of the whole `try` to be i32, both `try`and `catch` parts have to be i32:```try i32 ... block i32 ... endcatch ... block i32 ... endendend_function```---Previously we only handled consecutive `end`s or `end` before a `catch`.But now we have `delegate`, which serves like `end` for`try`-`delegate`. So we have to follow `delegate` too and mark itscorresponding `try` as i32 (the function's return type):```try i32 ...catch ... try i32 ;; Here ... delegate Nendend_function```Reviewed By: tlivelyDifferential Revision: https://reviews.llvm.org/D101036 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Thu, 22 Apr 2021 09:00:57 +0000 Heejin Ahn <aheejin@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#908643ad [WebAssembly] Split EH MIR tests into two filesCurrently exception.mir runs LateEHPrepare and CFGStackify, but sometests I'm planning to add shouldn't be run with LateEHPrepare, becauseit is convenient to only run CFGStackify when testing things like unwindmismatches and it is easier to add tests that are in phase right beforeCFGStackify. This splits existing exception.mir into two files;cfg-stackify-eh.mir will only run CFGStackify. Note that`eh_label_tests` tests both LateEHPrepare and CFGStackify, so it isstill in exception.mir. `rethrow_arg_tests` has been converted to thepost-LateEHPrepare form to be moved into cfg-stackify-eh.mir, likeremoving `CATCHRET` and such, because it does not really test anythingin LateEHPrepare.Reviewed By: dschuffDifferential Revision: https://reviews.llvm.org/D97175 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Mon, 22 Feb 2021 04:05:28 +0000 Heejin Ahn <aheejin@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#6a87ddac [WebAssembly] Massive instruction renamingSummary:An automated renaming of all the instructions listed athttps://github.com/WebAssembly/spec/issues/884#issuecomment-426433329as well as some similarly-named identifiers.Reviewers: aheejin, dschuff, aardappelSubscribers: sbc100, jgravelle-google, eraman, sunfish, jfb, llvm-commitsDifferential Revision: https://reviews.llvm.org/D56338llvm-svn: 350609 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Tue, 08 Jan 2019 06:25:55 +0000 Thomas Lively <tlively@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#ac764aa8 [WebAssembly] Fix immediate of rethrow when throwing to callerSummary:Currently when assigning depths 'rethrow' does not take the wholecontrol flow stack into accounts but only considers EH pad stacks. Whenassigning depth immmediates to rethrows, in normal cases it is donecorrectly but when a rethrow instruction throws up to a caller, i.e., weconvert a pseudo RETHROW_TO_CALLER instruction to a rethrow, itmistakenly compute the whole stack depth.Reviewers: dschuffSubscribers: sbc100, jgravelle-google, sunfish, llvm-commitsDifferential Revision: https://reviews.llvm.org/D53619llvm-svn: 345223 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Wed, 24 Oct 2018 23:31:24 +0000 Heejin Ahn <aheejin@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir#e76fa9ec [WebAssembly] CFG stackify support for exception handlingSummary:This adds support for exception handling to CFGStackify pass. This onlyadds TRY / END_TRY markers and DOES NOT yet fix unwind mismatches thatcan be created by the linearization of the CFG into the structural wasmformat. The mismatch fix will be added by following patches.In detail, this patch- Added support for TRY / END_TRY markers to support EH- Changed many static functions into class member functions as they taketoo many arguments now- Added several more bookeeping data structures- Refactored routines that decide where to insert markers, becausewithout refactoring this got too complicated as we added support for newkinds of markers (TRY/END_TRY).- Rewrote rethrow instructions' BB arguments to relative depths in EHpad stack.Reviewers: dschuff, sunfishSubscribers: sbc100, jgravelle-google, llvm-commitsDifferential Revision: https://reviews.llvm.org/D48273llvm-svn: 339967 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/cfg-stackify-eh.mir Thu, 16 Aug 2018 23:50:59 +0000 Heejin Ahn <aheejin@gmail.com>