From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2BC8F385F021; Sat, 19 Feb 2022 05:46:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BC8F385F021 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104603] wrong detection of g++ -Warray-bounds about downcast Date: Sat, 19 Feb 2022 05:46:19 +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: 10.3.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: 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-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2022 05:46:19 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104603 --- Comment #1 from Andrew Pinski --- -DA just changes inlining. This is just an inlining mess which you can see from the diagnostic on the trunk: In member function 'bool Base::isX() const', inlined from 'bool Base::operator=3D=3D(const Base&) const' at = :16:15, inlined from 'bool X::operator=3D=3D(const X&) const' at :10:51, inlined from 'bool Base::operator=3D=3D(const Base&) const' at = :16:63, inlined from 'bool X::operator=3D=3D(const X&) const' at :10:51, inlined from 'void f()' at :24:11: :4:29: warning: array subscript 2 is outside array bounds of 'X [1]' [-Warray-bounds] 4 | bool isX() const { return isX_; } | ^~~~ The warning happens before some other optimizations happen which allows GCC= to prove the function will just always return false ...=