public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/68124] New: [6 Regression] Many i386 test failures Date: Tue, 27 Oct 2015 22:34:00 -0000 [thread overview] Message-ID: <bug-68124-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68124 Bug ID: 68124 Summary: [6 Regression] Many i386 test failures Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com Target Milestone: --- On Linux/x86, r229459 gave FAIL: gcc.target/i386/avx2-vect-shift.c (internal compiler error) FAIL: gcc.target/i386/avx2-vect-shift.c (test for excess errors) FAIL: gcc.target/i386/pr51235.c (internal compiler error) FAIL: gcc.target/i386/pr51235.c (test for excess errors) FAIL: gcc.target/i386/pr58137.c (internal compiler error) FAIL: gcc.target/i386/pr58137.c (test for excess errors) FAIL: gcc.target/i386/pr64110.c (internal compiler error) FAIL: gcc.target/i386/pr64110.c (test for excess errors) r229452 is OK.
next reply other threads:[~2015-10-27 22:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-27 22:34 hjl.tools at gmail dot com [this message] 2015-10-27 23:44 ` [Bug target/68124] " hjl.tools at gmail dot com 2015-10-27 23:46 ` hjl.tools at gmail dot com 2015-10-28 1:29 ` hjl.tools at gmail dot com 2015-10-28 19:40 ` rth at gcc dot gnu.org 2015-10-28 20:16 ` rth at gcc dot gnu.org 2015-10-28 20:27 ` hjl.tools at gmail dot com 2015-10-28 20:46 ` rth at gcc dot gnu.org 2015-10-29 7:46 ` rth at gcc dot gnu.org 2015-10-29 14:17 ` hjl.tools at gmail dot com 2015-10-29 18:37 ` rth at gcc dot gnu.org 2015-10-29 18:44 ` rth 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-68124-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).