public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66721] New: [6 regression] gcc.target/i386/pr61403.c FAILs Date: Wed, 01 Jul 2015 14:14:00 -0000 [thread overview] Message-ID: <bug-66721-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66721 Bug ID: 66721 Summary: [6 regression] gcc.target/i386/pr61403.c FAILs Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- Host: i386-pc-solaris2.1[01], x86_64-unknown-linux-gnu Target: i386-pc-solaris2.1[01], x86_64-unknown-linux-gnu Build: i386-pc-solaris2.1[01], x86_64-unknown-linux-gnu For some time, gcc.target/i386/pr61403.c FAILs on Linux/x86 and Solaris/x86 (32-bit only): FAIL: gcc.target/i386/pr61403.c scan-assembler blend A reghunt identified the following patch as the culprit: 2015-06-08 Richard Biener <rguenther@suse.de> * tree-vect-stmts.c (vectorizable_load): Compute the pointer adjustment for gaps at the end of a SLP load group properly. * tree-vect-slp.c (vect_supported_load_permutation_p): Allow all permutations we can generate. (vect_transform_slp_perm_load): Use the correct group-size. Rainer
next reply other threads:[~2015-07-01 14:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-01 14:14 ro at gcc dot gnu.org [this message] 2015-07-01 14:14 ` [Bug tree-optimization/66721] " ro at gcc dot gnu.org 2015-07-02 8:15 ` 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-66721-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).