public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59124] [4.9/5/6 Regression] Wrong warnings "array subscript is above array bounds" Date: Fri, 11 Sep 2015 16:51:00 -0000 [thread overview] Message-ID: <bug-59124-4-XWchePOIVv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59124-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59124 --- Comment #22 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to baoshan from comment #21) > Don't you think the range value is strange? how it is possible the range > value is so big according the code? j = i - 1 is actually j = i + 4294967295 because of unsigned. Thus the problematic ranges: [test.c:9:13] # RANGE [4294967291, 4294967295] _51 = i_2 + 4294967290; are actually: [test.c:9:13] # RANGE [-5, -1] _51 = i_2 - 6; but this code should have not been generated. Those ranges do seem suspicious. Finding out how that block ends up with those ranges would be helpful. You probably need to debug vrp or (using -fopt-info) the point where gcc gives: test.c:7:3: note: loop turned into non-loop; it never loops. test.c:7:3: note: loop with 5 iterations completely unrolled >From gcc-bugs-return-497003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 11 17:00:30 2015 Return-Path: <gcc-bugs-return-497003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 68157 invoked by alias); 11 Sep 2015 17:00:30 -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 67049 invoked by uid 48); 11 Sep 2015 17:00:26 -0000 From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/67553] Saturating SSE/AVX instructions do not get optimized Date: Fri, 11 Sep 2015 17:00: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: 5.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: glisse at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: bug_status cf_reconfirmed_on component everconfirmed Message-ID: <bug-67553-4-yHlfx0iEXc@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67553-4@http.gcc.gnu.org/bugzilla/> References: <bug-67553-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-09/txt/msg00981.txt.bz2 Content-length: 606 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg553 Marc Glisse <glisse at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-09-11 Component|middle-end |rtl-optimization Ever confirmed|0 |1 --- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> --- Looks like SS_PLUS and SS_MINUS are missing in the constant folding code...
next prev parent reply other threads:[~2015-09-11 16:51 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-14 0:44 [Bug tree-optimization/59124] New: [4.8 " d.g.gorbachev at gmail dot com 2013-11-14 9:51 ` [Bug tree-optimization/59124] [4.8/4.9 " rguenth at gcc dot gnu.org 2013-11-14 17:56 ` d.g.gorbachev at gmail dot com 2013-11-21 14:39 ` rguenth at gcc dot gnu.org 2014-03-12 14:33 ` jakub at gcc dot gnu.org 2014-05-22 9:03 ` [Bug tree-optimization/59124] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:25 ` [Bug tree-optimization/59124] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-01-27 9:50 ` rguenth at gcc dot gnu.org 2015-01-27 10:59 ` rguenth at gcc dot gnu.org 2015-02-18 2:22 ` solar-gcc at openwall dot com 2015-02-18 4:37 ` solar-gcc at openwall dot com 2015-02-19 14:14 ` rguenth at gcc dot gnu.org 2015-02-24 13:09 ` rguenth at gcc dot gnu.org 2015-04-16 12:14 ` [Bug tree-optimization/59124] [4.8/4.9/5/6 " georgmueller at gmx dot net 2015-05-26 15:34 ` georgmueller at gmx dot net 2015-06-01 23:49 ` daniel at imperfectcode dot com 2015-06-23 8:16 ` rguenth at gcc dot gnu.org 2015-06-26 19:53 ` [Bug tree-optimization/59124] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:26 ` jakub at gcc dot gnu.org 2015-09-10 21:04 ` pangbw at gmail dot com 2015-09-11 0:29 ` manu at gcc dot gnu.org 2015-09-11 16:13 ` pangbw at gmail dot com 2015-09-11 16:51 ` manu at gcc dot gnu.org [this message] 2015-09-17 18:18 ` pangbw at gmail dot com 2015-09-17 19:02 ` pangbw at gmail dot com 2015-09-18 17:59 ` pangbw at gmail dot com 2015-09-18 18:32 ` manu at gcc dot gnu.org 2015-09-18 19:17 ` manu at gcc dot gnu.org 2015-09-18 21:11 ` pangbw at gmail dot com 2015-09-22 20:06 ` pangbw at gmail dot com 2021-01-05 9:14 ` [Bug tree-optimization/59124] [6 " szotsaki at gmail dot com
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-59124-4-XWchePOIVv@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: linkBe 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).