public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "az.zaafrani at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48052] loop not vectorized if index is "unsigned int"
Date: Thu, 07 May 2015 20:43:00 -0000	[thread overview]
Message-ID: <bug-48052-4-YBP9K48VbX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48052-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from zaafrani <az.zaafrani at gmail dot com> ---
Thank you for the feedback.

We excluded start value that is constant because it is already
working. To our knowledge, only when the start value is unknown and
the loop index type is of unsigned type that we fail to recognize
non-overflow for situations when it is possible to deduce so. For most
other cases, current analysis done in scev_probably_wraps_p seems to
be working fine. We also added the assumption of step equal 1 so that
we can make correct decision about non-overflow. So, basically we’d
rather catch few simple cases and make them work  then try to
generalize the scope and not being to prove much.


On Wed, May 6, 2015 at 1:56 AM, rguenth at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48052
>
> --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
> That's an interesting idea - your argument is that if niter analysis was able
> to compute an expression for the number of iterations and the cast we are
> looking at
> is a widening of a BIV then it is ok to assume the BIV does not wrap.
>
> Unfortunately this breaks down (eventually not in practice due to your
> exclusion of constant initial BIV value) for cases like
>
>
>   for (unsigned i = 3; i != 2; i+=7)
>     ;
>
> where niter analysis can still compute the number of iterations (I've made
> the numbers up, so maybe that loop will never terminate...).
>
> Still the idea is interesting as we might be able to record whether BIVs
> overflow or not.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>From gcc-bugs-return-485793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 07 20:45:26 2015
Return-Path: <gcc-bugs-return-485793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39374 invoked by alias); 7 May 2015 20:45:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39335 invoked by uid 48); 7 May 2015 20:45:22 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/48302] ICE: SIGSEGV in reposition_prologue_and_epilogue_notes (function.c:5662) with -fcrossjumping -fselective-scheduling2
Date: Thu, 07 May 2015 20:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amonakov at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-48302-4-sJ52wAsdQP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48302-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48302-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-05/txt/msg00633.txt.bz2
Content-length: 431

https://gcc.gnu.org/bugzilla/show_bug.cgi?idH302

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
.


  parent reply	other threads:[~2015-05-07 20:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 18:49 [Bug tree-optimization/48052] New: " vincenzo.innocente at cern dot ch
2011-03-10  0:21 ` [Bug tree-optimization/48052] " paolo.carlini at oracle dot com
2011-03-10  9:46 ` rguenth at gcc dot gnu.org
2011-03-10 10:22 ` paolo.carlini at oracle dot com
2011-03-10 10:54 ` vincenzo.innocente at cern dot ch
2011-03-10 11:22 ` paolo.carlini at oracle dot com
2011-03-10 11:31 ` paolo.carlini at oracle dot com
2011-03-11 10:16 ` vincenzo.innocente at cern dot ch
2011-03-11 10:26 ` rguenther at suse dot de
2011-03-14 10:08 ` vincenzo.innocente at cern dot ch
2015-05-04 19:33 ` az.zaafrani at gmail dot com
2015-05-06  6:57 ` rguenth at gcc dot gnu.org
2015-05-07 20:43 ` az.zaafrani at gmail dot com [this message]
2015-05-22 16:19 ` hiraditya at msn dot com
2015-06-02 10:19 ` amker at gcc dot gnu.org
2015-06-09  8:22 ` rguenth at gcc dot gnu.org
2015-06-23 13:23 ` evstupac at gmail dot com
2015-06-23 13:52 ` amker at gcc dot gnu.org
2015-06-24  2:34 ` amker 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-48052-4-YBP9K48VbX@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).