public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/31514] [gdb/testsuite] FAIL: gdb.ada/tagged-lookup.exp: only one CU expanded Date: Thu, 21 Mar 2024 08:00:49 +0000 [thread overview] Message-ID: <bug-31514-4717-iWRkzEn45Y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31514-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31514 --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- Tentative patch: ... diff --git a/gdb/testsuite/gdb.ada/tagged-lookup.exp b/gdb/testsuite/gdb.ada/tagged-lookup.exp index 4bc088ba8d5..3803319c505 100644 --- a/gdb/testsuite/gdb.ada/tagged-lookup.exp +++ b/gdb/testsuite/gdb.ada/tagged-lookup.exp @@ -52,7 +52,7 @@ gdb_test_multiple "print *the_local_var" "only one CU expanded" -lbl { exp_continue } -re -wrap ".* = \\\(n => $decimal\\\)" { - if {$found_pck + $found_pck2 == 1} { + if {$found_pck + $found_pck2 <= 1} { pass $gdb_test_name } else { fail $gdb_test_name ... It detects the fail with fix reverted for gcc-12 and gcc-13, though not before. And it make the test pass for gcc-12 and gcc-13 with the fix present. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-21 8:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-20 10:24 [Bug testsuite/31514] New: " vries at gcc dot gnu.org 2024-03-20 15:31 ` [Bug testsuite/31514] " vries at gcc dot gnu.org 2024-03-20 15:57 ` vries at gcc dot gnu.org 2024-03-20 16:37 ` vries at gcc dot gnu.org 2024-03-20 16:38 ` vries at gcc dot gnu.org 2024-03-21 7:34 ` vries at gcc dot gnu.org 2024-03-21 7:50 ` vries at gcc dot gnu.org 2024-03-21 8:00 ` vries at gcc dot gnu.org [this message] 2024-03-25 14:06 ` vries at gcc dot gnu.org 2024-03-25 14:28 ` cvs-commit at gcc dot gnu.org 2024-03-25 14:29 ` vries at gcc dot gnu.org
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=bug-31514-4717-iWRkzEn45Y@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).