public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42846] GCC sometimes ignores information about pointer target alignment
Date: Fri, 22 Jan 2010 16:30:00 -0000	[thread overview]
Message-ID: <20100122163003.15284.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42846-2476@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2010-01-22 16:30 -------
Yep.  I always fail to see why the vectorizer doesn't use the alignment
information present in from data-ref analysis:

t.i:9: note: === vect_analyze_data_refs ===
Creating dr for *D.2752_12
...
  (res = {p_4, +, 4}_1))
        base_address: p__3(D)
        offset from base address: 0
        constant offset from base address: 0
        step: 4
        aligned to: 128
        base_object: *(const aligned_real * restrict) p__3(D)

thus the base is aligned to 128 bits, offset and constant offset are
constant zero so the vectorizer should be able to compute alignment
of all accesses.

Still it says

t.i:9: note: === vect_analyze_data_refs_alignment ===
t.i:9: note: vect_compute_data_ref_alignment:
t.i:9: note: can't force alignment of ref: *D.2752_12
t.i:9: note: vect_compute_data_ref_alignment:
t.i:9: note: can't force alignment of ref: *D.2754_16
...
t.i:9: note: Vectorizing an unaligned access.
t.i:9: note: Vectorizing an unaligned access.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |irar at gcc dot gnu dot org,
                   |                            |rguenth at gcc dot gnu dot
                   |                            |org
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
           Keywords|                            |missed-optimization
   Last reconfirmed|0000-00-00 00:00:00         |2010-01-22 16:30:03
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42846


  parent reply	other threads:[~2010-01-22 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 15:12 [Bug tree-optimization/42846] New: " bredelin at ucla dot edu
2010-01-22 15:14 ` [Bug tree-optimization/42846] " bredelin at ucla dot edu
2010-01-22 16:30 ` rguenth at gcc dot gnu dot org [this message]
2010-01-24  7:42 ` irar at il dot ibm dot com
2010-01-24 11:52 ` rguenth at gcc dot gnu dot 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=20100122163003.15284.qmail@sourceware.org \
    --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).