public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from r13-71-g41e3db05d69740 Date: Thu, 05 May 2022 10:08:58 +0000 [thread overview] Message-ID: <bug-105486-4-m25ya8UYCM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105486-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105486 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com Target Milestone|--- |13.0 Status|WAITING |ASSIGNED Assignee|unassigned at gcc dot gnu.org |roger at nextmovesoftware dot com --- Comment #4 from Roger Sayle <roger at nextmovesoftware dot com> --- I think the mention of slp2 and pr104240.c in the bug report is bogus, and is a glitch in the automated regression checking scripts. The real problem is that my new test case for pr102950.c is failing on powerpc64. After a great deal of head scratching on why EVRP is producing different results on this platform, I've just realized that "char" must be unsigned on this target. Replacing "char" with "signed char" in gcc.dg/pr102950.c fixes the problem. I'll commit this fix as obvious. But I want to avoid anyone wasting time (like I did) trying to figure out why my patch should be the cause of an -flto failure of bb-slp-pr104240.c [which might be failure, but unrelated to the pr102950.c issue/bisect].
next prev parent reply other threads:[~2022-05-05 10:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 21:07 [Bug testsuite/105486] New: new test case gcc.dg/vect/bb-slp-pr104240.c from r13-89-gb3e98eb3396e16 fails seurer at gcc dot gnu.org 2022-05-05 7:16 ` [Bug testsuite/105486] new test case gcc.dg/vect/bb-slp-pr104240.c from r13-71-g41e3db05d69740 rguenth at gcc dot gnu.org 2022-05-05 8:42 ` cvs-commit at gcc dot gnu.org 2022-05-05 8:43 ` rguenth at gcc dot gnu.org 2022-05-05 10:08 ` roger at nextmovesoftware dot com [this message] 2022-05-05 12:31 ` cvs-commit at gcc dot gnu.org 2022-05-07 20:04 ` roger at nextmovesoftware dot com
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-105486-4-m25ya8UYCM@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).