From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A2EA1388B826; Fri, 3 Apr 2020 18:00:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A2EA1388B826 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585936850; bh=KDnQeE/VSTSGWLwnwZFNkfElSUeuWH1yYoI7Rwp5ics=; h=From:To:Subject:Date:In-Reply-To:References:From; b=U0EIWXGQfN4BZmLRVx/G8lebehe1EfkONVhY8hx6qVw3BYPVMYdTv9gY/BrCq6txI AUW+vcDy+RSR/7CqHLdluGqiq7hainmUhPC0fc7eojlw8toiSqL71kCSXB+3wqsr8X 1RpF0iv2f74UO2ZFsUPyaRF0H+N1TcsfU2m2xcfk= From: "dominik.b.czarnota+bugzilla at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/93641] Wrong strncmp and strncasecmp size arguments Date: Fri, 03 Apr 2020 18:00:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominik.b.czarnota+bugzilla at gmail dot com 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: Fri, 03 Apr 2020 18:00:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93641 --- Comment #8 from Dominik 'disconnect3d' Czarnota --- (In reply to Iain Sandoe from comment #7) > if the invoke.texi entry does not need a change, then this should now be > fixed, correct? It would be a good practice to fix the invoke.texi case too, so the bug doe= sn't get copied elsewhere, but anyway, the commits we can see above fixes all the listed code cases. I think the issue can then be marked as 'RESOLVED FIXED'. Thanks!=