public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60042] New: vectorizer still does too many dependence tests for himeno:jacobi Date: Mon, 03 Feb 2014 11:19:00 -0000 [thread overview] Message-ID: <bug-60042-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60042 Bug ID: 60042 Summary: vectorizer still does too many dependence tests for himeno:jacobi Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Created attachment 32026 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32026&action=edit himeno bench I still get himenobmtxpa.c:296:9: note: disable versioning for alias - max number of generated checks exceeded himenobmtxpa.c:296:9: note: too long list of versioning for alias run-time tests. I have a patch to remove some false dependences but still himenobmtxpa.c:296:9: note: improved number of alias checks from 31 to 21 and 21 is too much - 7 should suffice.
next reply other threads:[~2014-02-03 11:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-03 11:19 rguenth at gcc dot gnu.org [this message] 2014-02-03 11:23 ` [Bug tree-optimization/60042] " rguenth at gcc dot gnu.org 2014-02-03 13:51 ` rguenth at gcc dot gnu.org 2014-02-04 13:24 ` rguenth at gcc dot gnu.org 2014-02-04 13:34 ` rguenth at gcc dot gnu.org 2014-02-04 14:53 ` rguenth at gcc dot gnu.org 2014-02-04 15:09 ` rguenth at gcc dot gnu.org 2014-02-04 16:36 ` jakub at gcc dot gnu.org 2014-02-05 14:35 ` rguenth at gcc dot gnu.org 2014-04-14 13:57 ` 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-60042-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).