public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59892] out of bounds array access is misoptimized
Date: Tue, 21 Jan 2014 17:32:00 -0000	[thread overview]
Message-ID: <bug-59892-4-vWK9L13CVw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59892-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Lukasz Dorau from comment #3)
> (In reply to Markus Trippelsdorf from comment #2)
> > When v.hosts[0] or v.hosts[1] is NULL the loop is fine, so there is
> > no reason for a warning.
> > The testcase is obviously invalid.
> >
> But v.hosts[0] and v.hosts[1] do not have to be NULL. What's more, they are
> supposed not to be NULL. So why is it invalid?
> I understand that the loop is erroneous, but I do not understand why
> misoptimizing the code by dropping 'id < 2' loop condition is a right thing
> to do? And even without any warning?

Please note that you can use -fno-aggressive-loop-optimization if you 
dislike this behavior.

From http://gcc.gnu.org/bugs/:
 »if compiling with -fno-strict-aliasing -fwrapv
-fno-aggressive-loop-optimizations makes a difference, your code probably is
not correct«

And -Wno-aggressive-loop-optimizations doesn't handle early loop exits.
>From gcc-bugs-return-441133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 21 17:35:59 2014
Return-Path: <gcc-bugs-return-441133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20310 invoked by alias); 21 Jan 2014 17:35:58 -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 20271 invoked by uid 48); 21 Jan 2014 17:35:55 -0000
From: "lukasz.dorau at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59892] out of bounds array access is misoptimized
Date: Tue, 21 Jan 2014 17:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lukasz.dorau at intel dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59892-4-fxXeGMo8oZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59892-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: 2014-01/txt/msg02275.txt.bz2
Content-length: 154

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY892

--- Comment #5 from Lukasz Dorau <lukasz.dorau at intel dot com> ---
I see. Now I understand. Thanks!


      parent reply	other threads:[~2014-01-21 17:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 18:35 [Bug tree-optimization/59892] New: " alexei.starovoitov at gmail dot com
2014-01-20 18:43 ` [Bug tree-optimization/59892] " pinskia at gcc dot gnu.org
2014-01-20 18:47 ` trippels at gcc dot gnu.org
2014-01-21 17:24 ` lukasz.dorau at intel dot com
2014-01-21 17:32 ` trippels at gcc dot gnu.org [this message]

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-59892-4-vWK9L13CVw@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).