From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37685 invoked by alias); 18 Sep 2015 21:11:49 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 37642 invoked by uid 48); 18 Sep 2015 21:11:46 -0000 From: "pangbw at gmail dot com" 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, 18 Sep 2015 21:11: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: 4.8.3 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pangbw at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg01522.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D59124 --- Comment #31 from baoshan --- (In reply to Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez from comment #30) > (In reply to baoshan from comment #29) > > > However, it is clear that _14 =3D baz[_9] is executed only 5 times (n= ot 5 > > > times + 1). Why is this estimate wrong? > >=20 > > The max value of n is 6, so the max value of i is 5 as "i < n", then th= e max > > value of j is 4 as "j =3D i - 1" which means the max iterate times is 4. >=20 > True! Well, that reinforces my point that something is very wrong in the > estimation. What is it? At the pass "cunrolli", it infers the iterative times by checking the array= 's boundary, as we have "unsigned baz[6];", it would think the max value of iterative times is 6. >>From gcc-bugs-return-497545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 18 21:39:25 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28079 invoked by alias); 18 Sep 2015 21:39:25 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 28053 invoked by uid 48); 18 Sep 2015 21:39:21 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67631] brace initialization bug Date: Fri, 18 Sep 2015 21:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels 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: keywords bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg01523.txt.bz2 Content-length: 1233 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D67631 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Status|UNCONFIRMED |NEW Last reconfirmed| |2015-09-18 CC| |trippels at gcc dot gnu.org Ever confirmed|0 |1 Known to fail| |4.9.2, 5.2.1, 6.0 --- Comment #1 from Markus Trippelsdorf --- markus@x4 tmp % cat bra.ii class X { public: X (int); explicit operator unsigned (); }; unsigned foo () { return unsigned{ X (0) }; } markus@x4 tmp % icpc -Wall -Wextra -c -std=3Dc++14 bra.ii markus@x4 tmp % clang++ -Wall -Wextra -c -std=3Dc++14 bra.ii markus@x4 tmp % g++ -Wall -Wextra -c -std=3Dc++14 bra.ii bra.ii: In function =E2=80=98unsigned int foo()=E2=80=99: bra.ii:10:26: error: cannot convert =E2=80=98X=E2=80=99 to =E2=80=98unsigne= d int=E2=80=99 in initialization return unsigned{ X (0) }; ^ >>From gcc-bugs-return-497546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 18 21:48:54 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 35629 invoked by alias); 18 Sep 2015 21:48:54 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 35596 invoked by uid 48); 18 Sep 2015 21:48:50 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67632] explicit instantiation omits copy constructor and others Date: Fri, 18 Sep 2015 21:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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 cc resolution Message-ID: In-Reply-To: References: 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/msg01524.txt.bz2 Content-length: 572 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67632 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |trippels at gcc dot gnu.org Resolution|--- |WORKSFORME --- Comment #1 from Markus Trippelsdorf --- I cannot reproduce this issue with 4.9.3. Please update.