public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/108776] new test case c-c++-common/rotate-11.c from r12-9158-ga015ebe382cd6d fails Date: Mon, 15 May 2023 08:24:22 +0000 [thread overview] Message-ID: <bug-108776-4-veEjRR9YN1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108776 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:9410a52061ffe4a9e6ef8fd82f9c21d1874ff589 commit r12-9538-g9410a52061ffe4a9e6ef8fd82f9c21d1874ff589 Author: Richard Biener <rguenther@suse.de> Date: Thu May 11 09:13:31 2023 +0200 testsuite/108776 - avoid c-c++-common/rotate-11.c FAIL On the branch ranger isn't powerful enough to handle some cases appearing with logical-op-non-short-circuit evaluating to false causing FAILs of the testcase for ppc64le and s390x. The following foces logical-op-non-short-circuit to true for this testcase on the branch. PR testsuite/108776 * c-c++-common/rotate-11.c: Add --param logical-op-non-short-circuit=1.
next prev parent reply other threads:[~2023-05-15 8:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-13 16:23 [Bug testsuite/108776] New: " seurer at gcc dot gnu.org 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 [this message] 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-veEjRR9YN1@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).