From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/113477] New: rust/compile/torture/alt_patterns1.rs FAILs
Date: Thu, 18 Jan 2024 11:49:54 +0000 [thread overview]
Message-ID: <bug-113477-35322@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113477
Bug ID: 113477
Summary: rust/compile/torture/alt_patterns1.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: i386-pc-solaris2.11, sparc-sun-solaris2.11
Since the recent Rust import, one test FAILs on both 32 and 64-bit
Solaris/SPARC
and x86:
+FAIL: rust/compile/torture/alt_patterns1.rs -O0 (test for excess errors)
+FAIL: rust/compile/torture/alt_patterns1.rs -O1 (test for excess errors)
+FAIL: rust/compile/torture/alt_patterns1.rs -O2 (test for excess errors)
+FAIL: rust/compile/torture/alt_patterns1.rs -O2 -flto (test for excess
errors)
+FAIL: rust/compile/torture/alt_patterns1.rs -O2 -flto -flto-partition=none
(test for excess errors)
+FAIL: rust/compile/torture/alt_patterns1.rs -Os (test for excess errors)
Excess errors:
/vol/gcc/src/hg/master/local/gcc/testsuite/rust/compile/torture/alt_patterns1.rs:14:62:
error: variable 'z' is bound inconsistently across pattern alternatives [E0409]
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-01-18 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:49 ro at gcc dot gnu.org [this message]
2024-01-18 11:50 ` [Bug rust/113477] " ro at gcc dot gnu.org
2024-05-07 7:44 ` 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-113477-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).