public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64026] New: Many FAIL: ... scan-tree-dump-times vect "Vectorizing an unaligned access" 0 with -fpic
Date: Sat, 22 Nov 2014 13:34:00 -0000	[thread overview]
Message-ID: <bug-64026-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64026

            Bug ID: 64026
           Summary: Many FAIL: ... scan-tree-dump-times vect "Vectorizing
                    an unaligned access" 0 with -fpic
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ubizjak at gmail dot com

This is a recent regression. Comparing versions 5.0.0 20141120 (experimental)
[trunk revision 217836] [1] with 5.0.0 20141122 (experimental) [trunk revision
217961] [2], there are many vectorizer scan failures (using -fpic)

scan-tree-dump-times vect "Alignment of access forced using peeling"

and

scan-tree-dump-times vect "Vectorizing an unaligned access"

[1] https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg02192.html
[1] https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg02442.html


             reply	other threads:[~2014-11-22 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 13:34 ubizjak at gmail dot com [this message]
2014-11-22 13:36 ` [Bug tree-optimization/64026] " ubizjak at gmail dot com
2014-11-22 14:28 ` hjl.tools at gmail dot com
2014-11-22 17:31 ` hjl.tools at gmail dot com
2014-11-22 17:38 ` [Bug tree-optimization/64026] [5 Rehression] " hjl.tools at gmail dot com
2014-11-24 11:25 ` [Bug tree-optimization/64026] [5 Regression] " rguenth at gcc dot gnu.org
2014-11-24 11:29 ` ubizjak at gmail 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-64026-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: link
Be 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).