aboutsummaryrefslogtreecommitdiff
path: root/libgo
diff options
context:
space:
mode:
authorIan Lance Taylor <ian@gcc.gnu.org>2018-10-09 16:51:10 +0000
committerIan Lance Taylor <ian@gcc.gnu.org>2018-10-09 16:51:10 +0000
commit91b01194c9d1ecdf3c29afbfe1ee2201fb265e92 (patch)
tree759488d751d256a06340903250d6162f32cfc3d5 /libgo
parentc743425fce5517242dd67761fea298cd3459b4cc (diff)
downloadgcc-91b01194c9d1ecdf3c29afbfe1ee2201fb265e92.zip
gcc-91b01194c9d1ecdf3c29afbfe1ee2201fb265e92.tar.gz
gcc-91b01194c9d1ecdf3c29afbfe1ee2201fb265e92.tar.bz2
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 From-SVN: r264985
Diffstat (limited to 'libgo')
-rw-r--r--libgo/go/runtime/runtime_test.go3
1 files changed, 3 insertions, 0 deletions
diff --git a/libgo/go/runtime/runtime_test.go b/libgo/go/runtime/runtime_test.go
index 995ce25..222679e0 100644
--- a/libgo/go/runtime/runtime_test.go
+++ b/libgo/go/runtime/runtime_test.go
@@ -166,6 +166,9 @@ func TestSetPanicOnFault(t *testing.T) {
}
func testSetPanicOnFault(t *testing.T, addr uintptr, nfault *int) {
+ if strings.Contains(Version(), "llvm") {
+ t.Skip("LLVM doesn't support non-call exception")
+ }
if GOOS == "nacl" {
t.Skip("nacl doesn't seem to fault on high addresses")
}