public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/26197] rust FAILs with rustc 1.36.0 and llvm 7
Date: Mon, 17 Aug 2020 16:49:12 +0000 [thread overview]
Message-ID: <bug-26197-4717-V8grJ4lWlX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26197-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26197
--- Comment #24 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=326afb722951cacc6131e2d6d1511986748ca017
commit 326afb722951cacc6131e2d6d1511986748ca017
Author: Tom Tromey <tromey@adacore.com>
Date: Mon Aug 17 10:45:49 2020 -0600
Update xfail pattern in gdb.rust/simple.exp
In PR rust/26197, Tom de Vries notes that the variant part rewrite
caused some regressions for the Rust compiler he has. This compiler
is unusual in that it combines a relatively recent rustc with a
relatively old LLVM -- so variant parts are not emitted using DWARF.
Most of the bugs in that PR were already fixed by earlier patches, but
some lingered. After some research we found that some of these never
did work -- which is consistent with the investigations we did into
the debug info -- but instead were xfail'd. This patch updates the
xfails to cope with the new output. (After this, just one failure
remains.)
Tom de Vries tested this using his rustc and suggested a fix that
appears in this version.
gdb/testsuite/ChangeLog
2020-08-17 Tom de Vries <tdevries@suse.de>
Tom Tromey <tromey@adacore.com>
PR rust/26197:
* gdb.rust/simple.exp (xfail_pattern): Update for new failure.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-17 16:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:01 [Bug rust/26197] New: " vries at gcc dot gnu.org
2020-07-02 15:01 ` [Bug rust/26197] " vries at gcc dot gnu.org
2020-07-02 15:02 ` vries at gcc dot gnu.org
2020-07-02 15:02 ` vries at gcc dot gnu.org
2020-07-02 15:02 ` vries at gcc dot gnu.org
2020-07-06 9:28 ` vries at gcc dot gnu.org
2020-07-12 21:20 ` tromey at sourceware dot org
2020-07-12 21:35 ` tromey at sourceware dot org
2020-07-13 9:25 ` vries at gcc dot gnu.org
2020-07-13 9:31 ` vries at gcc dot gnu.org
2020-07-14 1:52 ` tromey at sourceware dot org
2020-07-21 20:39 ` tromey at sourceware dot org
2020-07-22 12:55 ` brobecker at gnat dot com
2020-07-22 19:37 ` tromey at sourceware dot org
2020-07-22 19:40 ` tromey at sourceware dot org
2020-07-22 20:02 ` tromey at sourceware dot org
2020-07-22 20:13 ` tromey at sourceware dot org
2020-08-05 16:11 ` cvs-commit at gcc dot gnu.org
2020-08-05 17:52 ` tromey at sourceware dot org
2020-08-05 19:34 ` vries at gcc dot gnu.org
2020-08-12 21:31 ` tromey at sourceware dot org
2020-08-13 11:26 ` vries at gcc dot gnu.org
2020-08-13 12:43 ` tromey at sourceware dot org
2020-08-13 12:46 ` vries at gcc dot gnu.org
2020-08-13 14:13 ` tromey at sourceware dot org
2020-08-15 6:10 ` vries at gcc dot gnu.org
2020-08-17 16:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-17 17:04 ` tromey at sourceware dot org
2020-08-17 17:09 ` tromey at sourceware dot org
2020-08-18 9:02 ` vries at gcc dot gnu.org
2020-08-18 9:34 ` vries at gcc dot gnu.org
2020-09-08 16:42 ` tromey at sourceware dot org
2020-09-10 18:39 ` tromey at sourceware dot org
2020-09-10 18:43 ` tromey at sourceware dot org
2020-09-15 15:27 ` cvs-commit at gcc dot gnu.org
2020-09-15 15:48 ` cvs-commit at gcc dot gnu.org
2020-09-15 15:48 ` tromey at sourceware dot 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-26197-4717-V8grJ4lWlX@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).