| commit | a585ef50c7ebaf36655f1b405010e7f6cfbce81f | |
| author | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Tue, 9 Oct 2018 16:51:10 +0000 (9 16:51 +0000) | ||
| committer | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Tue, 9 Oct 2018 16:51:10 +0000 (9 16:51 +0000) | ||
| tree | 759488d751d256a06340903250d6162f32cfc3d5 | treesnapshot (tar.gz zip) |
| parent | f5edd321a43ac1c07145d6759cabddedd5c4f110 | commitdiff |
runtime: skip testSetPanicOnFault for gollvm
LLVM doesn't support non-call exception. This test was passing
more or less by luck: if the faulting instruction is between two
calls with the same landing pad (in instruction layout order,
not the program's logic order), it generates a merged PC range
that covers the faulting instruction. If the instruction layout
order changes, or it uses two different (but may be degenerate)
landing pads, this doesn't work.
Reviewed-on: https://go-review.googlesource.com/c/140517
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@264985 138bc75d-0d04-0410-961f-82ee72b054a4
LLVM doesn't support non-call exception. This test was passing
more or less by luck: if the faulting instruction is between two
calls with the same landing pad (in instruction layout order,
not the program's logic order), it generates a merged PC range
that covers the faulting instruction. If the instruction layout
order changes, or it uses two different (but may be degenerate)
landing pads, this doesn't work.
Reviewed-on: https://go-review.googlesource.com/c/140517
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@264985 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/go/gofrontend/MERGE | diffblobblamehistory | |
| libgo/go/runtime/runtime_test.go | diffblobblamehistory |