public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/113865] New: FAIL: rust/execute/torture/issue-2187.rs   -O0  output pattern test
Date: Sat, 10 Feb 2024 17:20:35 +0000	[thread overview]
Message-ID: <bug-113865-35322@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113865

            Bug ID: 113865
           Summary: FAIL: rust/execute/torture/issue-2187.rs   -O0  output
                    pattern test
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rust
          Assignee: unassigned at gcc dot gnu.org
          Reporter: danglin at gcc dot gnu.org
                CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org
  Target Milestone: ---

spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir64/gcc/testsuite/rust/../../gccrs
-B/home/dave/gnu/gcc/objdir64/gcc/testsuite/rust/../../
/home/dave/gnu/gcc/gcc/g
cc/testsuite/rust/execute/torture/issue-2187.rs -fdiagnostics-plain-output
-frus
t-incomplete-and-experimental-compiler-do-not-use -O0 -lm -o ./issue-2187.exe
PASS: rust/execute/torture/issue-2187.rs   -O0  (test for excess errors)
Setting LD_LIBRARY_PATH to
.:.:/home/dave/gnu/gcc/objdir64/gcc:/home/dave/gnu/gc
c/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/src/.libs
Execution timeout is: 300
spawn [open ...]
L1
L2

PASS: rust/execute/torture/issue-2187.rs   -O0  execution test
FAIL: rust/execute/torture/issue-2187.rs   -O0  output pattern test
Output was:
L1
L2


Should match:
L1
L2
L3
L4

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2024-02-10 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 17:20 danglin at gcc dot gnu.org [this message]
2024-02-12  8:43 ` [Bug rust/113865] " 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-113865-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).