public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/108776] New: new test case c-c++-common/rotate-11.c from r12-9158-ga015ebe382cd6d fails Date: Mon, 13 Feb 2023 16:23:15 +0000 [thread overview] Message-ID: <bug-108776-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108776 Bug ID: 108776 Summary: new test case c-c++-common/rotate-11.c from r12-9158-ga015ebe382cd6d fails Product: gcc Version: 12.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:a015ebe382cd6d0beab9db4ad33fbd252b7e2339, r12-9158-ga015ebe382cd6d make -k check-gcc RUNTESTFLAGS="dg.exp=c-c++-common/rotate-11.c" FAIL: c-c++-common/rotate-11.c -Wc++-compat scan-tree-dump-times optimized " r<< " 5 FAIL: c-c++-common/rotate-11.c -std=gnu++98 scan-tree-dump-times optimized " r<< " 5 FAIL: c-c++-common/rotate-11.c -std=gnu++14 scan-tree-dump-times optimized " r<< " 5 FAIL: c-c++-common/rotate-11.c -std=gnu++17 scan-tree-dump-times optimized " r<< " 5 FAIL: c-c++-common/rotate-11.c -std=gnu++20 scan-tree-dump-times optimized " r<< " 5 # of expected passes 2 # of expected passes 8 # of unexpected failures 1 # of unexpected failures 4 commit a015ebe382cd6d0beab9db4ad33fbd252b7e2339 (HEAD, refs/bisect/bad) Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Jan 19 10:00:51 2023 +0100 forwprop: Further fixes for simplify_rotate [PR108440]
next reply other threads:[~2023-02-13 16:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-13 16:23 seurer at gcc dot gnu.org [this message] 2023-05-11 7:13 ` [Bug testsuite/108776] " rguenth at gcc dot gnu.org 2023-05-11 7:21 ` jakub at gcc dot gnu.org 2023-05-11 7:31 ` rguenth at gcc dot gnu.org 2023-05-15 8:24 ` cvs-commit at gcc dot gnu.org 2023-05-15 8:24 ` 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-108776-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).