public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] add xfails to gdb.base/complex-parts.exp when testing with clang Date: Mon, 12 Sep 2022 12:18:13 +0000 (GMT) [thread overview] Message-ID: <20220912121813.ACA0F38515CA@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fbdc50d2c7ce12458aa925ea3dd8512f652929bd commit fbdc50d2c7ce12458aa925ea3dd8512f652929bd Author: Bruno Larsen <blarsen@redhat.com> Date: Wed Jul 20 16:44:34 2022 -0300 add xfails to gdb.base/complex-parts.exp when testing with clang clang doesn't add encoding to the name of complex variables, only says that the type name is complex, making the relevant tests fail. This patch adds the xfails to the tests that expect the variable name to include it. Diff: --- gdb/testsuite/gdb.base/complex-parts.exp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/gdb/testsuite/gdb.base/complex-parts.exp b/gdb/testsuite/gdb.base/complex-parts.exp index e67fd482268..7fa94c72cd4 100644 --- a/gdb/testsuite/gdb.base/complex-parts.exp +++ b/gdb/testsuite/gdb.base/complex-parts.exp @@ -30,8 +30,13 @@ gdb_test "p z1" " = 1.5 \\+ 4.5i" gdb_test "p z2" " = 2.5 \\+ -5.5i" gdb_test "p z3" " = 3.5 \\+ 6.5i" +# The following 3 tests are broken for Clang. +# More info at https://github.com/llvm/llvm-project/issues/52996. +if {[test_compiler_info clang-*-*]} { setup_xfail *-*-* } gdb_test "ptype z1" " = complex double" +if {[test_compiler_info clang-*-*]} { setup_xfail *-*-* } gdb_test "ptype z2" " = complex float" +if {[test_compiler_info clang-*-*]} { setup_xfail *-*-* } gdb_test "ptype z3" " = complex long double" with_test_prefix "double imaginary" {
reply other threads:[~2022-09-12 12:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220912121813.ACA0F38515CA@sourceware.org \ --to=blarsen@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).