From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: qiyaoltc@gmail.com (Yao Qi), dje@google.com (Doug Evans),
brobecker@adacore.com (Joel Brobecker),
gdb-patches@sourceware.org (gdb-patches)
Subject: Re: Several regressions and we branch soon.
Date: Mon, 20 Jul 2015 15:08:00 -0000 [thread overview]
Message-ID: <87io9eyih6.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <20150710162332.182E6B042@oc7340732750.ibm.com> (Ulrich Weigand's message of "Fri, 10 Jul 2015 18:23:32 +0200 (CEST)")
On Fri, Jul 10 2015, Ulrich Weigand wrote:
> Andreas Arnez wrote:
>> On Fri, Jul 10 2015, Yao Qi wrote:
>
>> GCC5 on ppc64le emits the ABI warning even in absence of "-mcpu=".
>> Again it should help to add "-Wno-psabi".
>
> Yes, for ppc64 we definitely should add -Wno-psabi.
OK.
>> Yes. But in this case no vector ABI is used, because that test machine
>> does not have a vector facility and because -march=native is not
>> supported by GCC (yet). Thus vector return values are not passed in
>> vector registers, but according to RETURN_VALUE_STRUCT_CONVENTION. And
>> then we hit the problem that displaying such return values is not
>> supported by GDB: https://sourceware.org/bugzilla/show_bug.cgi?id=8549
>
> Hmm. Since this is a separate problem independent of vector support,
> maybe this test case should accept the failure to display struct return
> values, and pass the test (or maybe KFAIL?).
Sure, that's an option. I prefer KFAIL, such that it's easy to find
(and remove) when the bug is fixed.
Here's a patch for both of the suggested changes. OK to apply?
-- >8 --
Subject: [PATCH] gnu_vector.exp: Avoid some more known FAILs
This avoids two more types of FAILs with the gnu_vector test case.
First, for POWER targets newer GCCs emit an ABI note when invoked with
"-mcpu=native". Then the test case fell back to non-native compile,
producing code for a non-vector ABI. But that is not supported by GDB.
Thus the compiler note is now suppressed with "-Wno-psabi".
Second, on s390 the test case produced FAILs after falling back to a
non-vector ABI when using "finish" or "return" in a vector-valued
function. This was due to a long-standing known bug (Bug 8549). This
case is now detected, and KFAILs are emitted instead.
gdb/testsuite/ChangeLog:
* gdb.base/gnu_vector.exp: Try compilation with "-mcpu=native
-Wno-psabi" if "-mcpu=native" fails. For the tests with "finish"
and "return" use KFAIL when GDB can not read/write the vector
return value.
---
gdb/testsuite/gdb.base/gnu_vector.exp | 57 +++++++++++++++++++++++++++--------
1 file changed, 44 insertions(+), 13 deletions(-)
diff --git a/gdb/testsuite/gdb.base/gnu_vector.exp b/gdb/testsuite/gdb.base/gnu_vector.exp
index 173da4d..0bef3f8 100644
--- a/gdb/testsuite/gdb.base/gnu_vector.exp
+++ b/gdb/testsuite/gdb.base/gnu_vector.exp
@@ -25,11 +25,19 @@ standard_testfile .c
# without a CPU option. If all variants fail, assume that the
# compiler can not handle GNU vectors.
-if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" ${binfile} executable {debug quiet additional_flags=-mcpu=native}] != ""
- && [gdb_compile "${srcdir}/${subdir}/${srcfile}" ${binfile} executable {debug quiet additional_flags=-march=native}] != ""
- && [gdb_compile "${srcdir}/${subdir}/${srcfile}" ${binfile} executable {debug quiet}] != ""} {
- untested "compiler can't handle the vector_size attribute?"
- return -1
+proc do_compile { {opts {}} } {
+ global srcdir subdir srcfile binfile
+ set ccopts {debug quiet}
+ foreach opt $opts {lappend ccopts "additional_flags=$opt"}
+ gdb_compile "${srcdir}/${subdir}/${srcfile}" "$binfile" executable $ccopts
+}
+
+if { [do_compile {-mcpu=native}] != ""
+ && [do_compile {-mcpu=native -Wno-psabi}] != ""
+ && [do_compile {-march=native}] != ""
+ && [do_compile] != ""} {
+ untested "compiler can't handle vector_size attribute?"
+ return -1
}
clean_restart ${binfile}
@@ -195,14 +203,37 @@ gdb_test "print add_structvecs(i2, (struct just_int2)\{2*i2\}, (struct two_int2)
gdb_test "print add_singlevecs((char1) \{6\}, (int1) \{12\}, (double1) \{24\})" "= \\{42\\}" \
"call add_singlevecs"
-# Test vector return value handling with "finish" and "return".
+# Test "finish" from vector-valued function.
gdb_breakpoint "add_some_intvecs"
gdb_continue "add_some_intvecs"
-gdb_test "finish" "Value returned is .* = \\{10, 20, 48, 72\\}" \
- "finish shows vector return value"
+set test "finish shows vector return value"
+gdb_test_multiple "finish" $test {
+ -re "Value returned is .* = \\{10, 20, 48, 72\\}.*$gdb_prompt $" {
+ pass $test
+ }
+ -re "Value returned has type: .* Cannot determine contents.*$gdb_prompt $" {
+ kfail "gdb/8549" $test
+ }
+}
+
+# Test "return" from vector-valued function.
gdb_continue "add_some_intvecs"
-gdb_test "return (int4) \{4, 2, 7, 6\}" \
- "#0 .* main .*" \
- "set vector return value" \
- "Make add_some_intvecs return now. .y or n.*" "y"
-gdb_test "continue" "4 2 7 6\r\n.*" "verify vector return value"
+set test "set vector return value"
+set ok 1
+gdb_test_multiple "return (int4) \{4, 2, 7, 6\}" $test {
+ -re "#0 .* main .*$gdb_prompt $" {
+ if { $ok } {
+ pass $test
+ gdb_test "continue" "4 2 7 6\r\n.*" "verify vector return value"
+ }
+ }
+ -re "The location .* is unknown.\r\n.* return value .* will be ignored.\r\n" {
+ kfail "gdb/8549" $test
+ set ok 0
+ exp_continue
+ }
+ -re "Make add_some_intvecs return now. .y or n. $" {
+ send_gdb "y\n"
+ exp_continue
+ }
+}
--
2.4.6
prev parent reply other threads:[~2015-07-20 15:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 18:31 Doug Evans
2015-06-23 18:55 ` Patrick Palka
2015-06-23 19:03 ` Doug Evans
2015-06-23 20:17 ` Keith Seitz
2015-06-23 20:53 ` Doug Evans
2015-06-23 21:45 ` Patrick Palka
2015-06-24 11:55 ` Yao Qi
2015-06-25 16:35 ` Tedeschi, Walfred
2015-07-01 8:49 ` Yao Qi
[not found] ` <AC542571535E904D8E8ADAE745D60B1944445D44@IRSMSX104.ger.corp.intel.com>
2015-07-01 9:30 ` Walfred Tedeschi
2015-07-02 10:09 ` Yao Qi
2015-07-02 15:34 ` Yao Qi
2015-07-02 16:19 ` [PATCH] Don't throw an error in "show mpx bound" implementation Patrick Palka
2015-07-06 9:31 ` Yao Qi
2015-06-24 10:21 ` Several regressions and we branch soon Yao Qi
[not found] ` <87lhf8yz90.fsf@br87z6lw.de.ibm.com>
2015-06-25 13:34 ` Doug Evans
2015-06-25 18:00 ` Andreas Arnez
2015-06-30 15:21 ` Yao Qi
2015-06-30 18:09 ` Andreas Arnez
2015-07-01 8:01 ` Yao Qi
2015-07-10 9:33 ` Yao Qi
2015-07-10 16:12 ` Andreas Arnez
2015-07-10 16:23 ` Ulrich Weigand
2015-07-20 15:08 ` Andreas Arnez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io9eyih6.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox