public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/62012] Loop is not vectorized after function inlining (SCEV)
Date: Tue, 09 Sep 2014 14:01:00 -0000 [thread overview]
Message-ID: <bug-62012-4-uMG4Hj9x9f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62012-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62012
--- Comment #5 from Yuri Rumyantsev <ysrumyan at gmail dot com> ---
You can close this bug as fixed/resolved (see my comment).
Thanks.
Yuri.
2014-09-08 15:29 GMT+04:00 rguenth at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org>:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62012
>
> Richard Biener <rguenth at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |WAITING
> Last reconfirmed| |2014-09-08
> Ever confirmed|0 |1
>
> --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
> So it's independend of LTO.
>
> Confirmed. We have
>
> _28 = &MEM[(struct Array *)&fa + 256B].a[0] + _3;
> *_28 = u_23;
>
> which SCEV messes up because it ends up with
>
> (instantiate_scev
> (instantiate_below = 4)
> (evolution_loop = 1)
> (chrec = &MEM[(struct Array *)&fa + 256B].a[0])
> (res = &MEM[(struct Array *)&fa + 256B].a[0]))
> (instantiate_scev
> (instantiate_below = 4)
> (evolution_loop = 1)
> (chrec = {(long unsigned int) first_6(D) * 4, +, 4}_1)
> (res = {(long unsigned int) first_6(D) * 4, +, 4}_1))
> (set_scalar_evolution
> instantiated_below = 4
> (scalar = _13)
> (scalar_evolution = {&MEM[(struct Array *)&fa + 256B].a[(sizetype)
> first_6(D)], +, 4}_1))
> )
> failed: evolution of base is not affine.
>
> Not sure why it thinks that.
>
> Btw, on trunk we now vectorize this just fine probably because of the fix
> for PR63148 which avoids moving first_6 * 4 inside the array-ref and we
> get
>
> (scalar_evolution = {&MEM[(struct Array *)&fa + 256B].a[0] + (sizetype)
> ((long unsigned int) first_6(D) * 4), +, 4}_1))
> )
> success.
>
> instead.
>
> So - can you re-check please?
>
> --
> You are receiving this mail because:
> You reported the bug.
next prev parent reply other threads:[~2014-09-09 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 14:48 [Bug tree-optimization/62012] New: " ysrumyan at gmail dot com
2014-08-04 14:51 ` [Bug tree-optimization/62012] " ysrumyan at gmail dot com
2014-09-08 10:59 ` ysrumyan at gmail dot com
2014-09-08 11:29 ` rguenth at gcc dot gnu.org
2014-09-09 13:57 ` ysrumyan at gmail dot com
2014-09-09 14:01 ` ysrumyan at gmail dot com [this message]
2014-09-09 14:04 ` 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-62012-4-uMG4Hj9x9f@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).