From 8216cda9b44352ed26e93c32fb24642b6283b9da Mon Sep 17 00:00:00 2001 From: Kevin Buettner Date: Sat, 13 May 2000 01:38:05 +0000 Subject: For IA-64, allow ``finish'' to land on caller rather than on next executable line after the caller. --- gdb/testsuite/gdb.base/step-test.exp | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'gdb/testsuite/gdb.base') diff --git a/gdb/testsuite/gdb.base/step-test.exp b/gdb/testsuite/gdb.base/step-test.exp index 47d4572..652192a 100644 --- a/gdb/testsuite/gdb.base/step-test.exp +++ b/gdb/testsuite/gdb.base/step-test.exp @@ -75,8 +75,10 @@ gdb_test "step" ".*${decimal}.*myglob.*" "step into" # instruction, which is attributed to the line containing the function # call? -# On PA64 we end up at a different instruction than PA32 -if { [istarget "hppa2.0w-hp-hpux*"] } { +# On PA64, we end up at a different instruction than PA32. +# On IA-64, we also end up on callee instead of on the next line due +# to the restoration of the global pointer (which is a caller-save). +if { [istarget "hppa2.0w-hp-hpux*"] || [istarget "ia64-*-*"]} { send_gdb "finish\n" gdb_expect { -re ".*${decimal}.*a.*5.*= a.*3.*$gdb_prompt $" { pass "step out 1" } @@ -171,8 +173,10 @@ gdb_expect { pass "stepi: finish call" } -re ".*${decimal}.*callee.*STEPI.*$gdb_prompt $" { - # On PA64 we end up at a different instruction than PA32 - if { [istarget "hppa2.0w-hp-hpux*"] } { + # On PA64, we end up at a different instruction than PA32. + # On IA-64, we end up on callee instead of on the following line due + # to the restoration of the global pointer. + if { [istarget "hppa2.0w-hp-hpux*"] || [istarget "ia64-*-*"] } { pass "stepi: finish call 2" } else { fail "stepi: finish call 2" -- cgit v1.1