From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/113472] New: rust/compile/issue-1446.rs FAILs
Date: Thu, 18 Jan 2024 10:51:34 +0000 [thread overview]
Message-ID: <bug-113472-35322@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113472
Bug ID: 113472
Summary: rust/compile/issue-1446.rs FAILs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rust
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org
Target Milestone: ---
Target: sparc-sun-solaris2.11
Since the recent Rust import, a test FAILs on 32 and 64-bit Solaris/SPARC:
+FAIL: rust/compile/issue-1446.rs (test for excess errors)
Excess errors:
/vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/issue-1446.rs:8:14:
error: no method named 'swap_bytes' found in the current scope [E0599]
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-01-18 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:51 ro at gcc dot gnu.org [this message]
2024-01-18 10:52 ` [Bug rust/113472] " ro at gcc dot gnu.org
2024-02-10 17:05 ` danglin at gcc dot gnu.org
2024-05-07 7:43 ` rguenth 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-113472-35322@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.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).