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: Tue, 15 Sep 2020 15:27:51 +0000 [thread overview]
Message-ID: <bug-26197-4717-bhJvqOhyhu@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 #32 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=08cc37dd042338209c8e2aa5db04aef2ecb5c62b
commit 08cc37dd042338209c8e2aa5db04aef2ecb5c62b
Author: Tom Tromey <tromey@adacore.com>
Date: Tue Sep 15 09:27:01 2020 -0600
Avoid running one Rust test against older LLVM
LLVM 8.0 introduced some changes to let the Rust compiler emit DWARF
variant parts. Before this change, the compiler would emit two types
with the same name, and unfortunately gdb happens to pick the wrong
one. So, this patch disables the test when using an older version of
LLVM.
gdb/testsuite/ChangeLog
2020-09-15 Tom Tromey <tromey@adacore.com>
PR rust/26197:
* lib/rust-support.exp (rust_llvm_version): New proc.
* gdb.rust/simple.exp: Check rust_llvm_version.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-15 15:27 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
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 [this message]
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-bhJvqOhyhu@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).