public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41464] vector loads are unnecessarily split into high and low loads
Date: Sun, 27 Sep 2009 08:06:00 -0000 [thread overview]
Message-ID: <20090927080615.13730.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41464-10309@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from irar at il dot ibm dot com 2009-09-27 08:06 -------
(In reply to comment #1)
> The interesting thing is that data-ref analysis sees 128bit alignment but
> the vectorizer still produces
> vect_var_.24_59 = M*vect_p.20_57{misalignment: 0};
> D.2564_12 = *D.2563_11;
> vect_var_.25_61 = vect_var_.24_59 * vect_cst_.26_60;
> D.2565_13 = D.2564_12 * 2.2999999523162841796875e+0;
> M*vect_p.27_64{misalignment: 0} = vect_var_.25_61;
> thus, unknown misalignment.
> (instantiate_scev
> (instantiate_below = 3)
> (evolution_loop = 1)
> (chrec = {i_10(D), +, 4}_1)
> (res = {i_10(D), +, 4}_1))
> base_address: i_10(D)
> offset from base address: 0
> constant offset from base address: 0
> step: 4
> aligned to: 128
> base_object: *i_10(D)
> Creating dr for *D.2562_7
> (res = {f_6(D), +, 4}_1))
> base_address: f_6(D)
> offset from base address: 0
> constant offset from base address: 0
> step: 4
> aligned to: 128
> base_object: *f_6(D)
> t2.i:5: note: === vect_enhance_data_refs_alignment ===
> t2.i:5: note: Vectorizing an unaligned access.
> t2.i:5: note: Vectorizing an unaligned access.
"aligned to" refers to the offset misalignment and not to the misalignment of
base.
attribute aligned works only for arrays, i.e., declarations, and not for
pointer arguments. For pointers the vectorizer only checks TYPE_ALIGN_UNIT of
the base type.
Ira
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41464
next prev parent reply other threads:[~2009-09-27 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 23:14 [Bug tree-optimization/41464] New: " nmiell at comcast dot net
2009-09-25 9:06 ` [Bug tree-optimization/41464] " rguenth at gcc dot gnu dot org
2009-09-25 17:12 ` nmiell at comcast dot net
2009-09-25 17:34 ` ubizjak at gmail dot com
2009-09-27 8:06 ` irar at il dot ibm dot com [this message]
2009-09-27 9:43 ` rguenther at suse dot de
2009-09-27 9:56 ` irar at il dot ibm dot com
2010-01-24 11:52 ` rguenth at gcc dot gnu dot org
2010-01-24 12:10 ` rguenth at gcc dot gnu dot org
2010-02-04 20:29 ` bredelin at ucla dot edu
[not found] <bug-41464-4@http.gcc.gnu.org/bugzilla/>
2021-12-13 0:09 ` pinskia 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=20090927080615.13730.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).