From: Richard Guenther <richard.guenther@gmail.com>
To: roy rosen <roy.1rosen@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: vectorization, scheduling and aliasing
Date: Mon, 26 Apr 2010 14:34:00 -0000 [thread overview]
Message-ID: <m2s84fc9c001004260731s9a185937l10c2f703ac94846f@mail.gmail.com> (raw)
In-Reply-To: <j2obba479b11004260642jb2d2769aya4e2f487be3d1f6d@mail.gmail.com>
On Mon, Apr 26, 2010 at 3:42 PM, roy rosen <roy.1rosen@gmail.com> wrote:
> Hi Richard,
>
> Here is the relevant block from the dump:
>
> <bb 3>:
> __vect_var__26_6 = *__vect_p_14_19;
> *__vect_p_18_25 = __vect_var__26_6;
> # PT = nonlocal { __PARM_RESTRICT_2 } (restr)
> __vect_p_22_11 = __vect_p_14_19 + 8;
> # PT = nonlocal { __PARM_RESTRICT_1 } (restr)
> __vect_p_27_12 = __vect_p_18_25 + 8;
> __vect_var__26_45 = *__vect_p_22_11;
> *__vect_p_27_12 = __vect_var__26_45;
>
> I guess that it recognizes the restrict pointer so I don't understand
> why later it creates a dependency between the insns.
> Do you see here something relevant?
No, it looks good. At least if both __vect_p_22 and __vect_p_27
are restrict qualified.
The RTL dumps should show *__vect_p_27_12 and similar
expressions in their MEM_ATTRS as well.
Note that IVOPTs is known to not preserve alias information so
you might want to try -fno-ivopts
> Thanks, Roy.
>
next prev parent reply other threads:[~2010-04-26 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 8:40 roy rosen
2010-04-14 11:07 ` Richard Guenther
2010-04-22 16:22 ` roy rosen
2010-04-23 12:12 ` Richard Guenther
2010-04-26 7:57 ` roy rosen
2010-04-26 11:24 ` Richard Guenther
2010-04-26 13:51 ` roy rosen
2010-04-26 14:34 ` Richard Guenther [this message]
2010-04-27 8:04 ` roy rosen
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=m2s84fc9c001004260731s9a185937l10c2f703ac94846f@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=roy.1rosen@gmail.com \
/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).