From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0C531386F43C; Tue, 28 Apr 2020 22:36:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C531386F43C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1588113361; bh=YYpaAqcS/2Mb7gsf19xfTyjwWMAFyLako56k4J0Z4Rw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Yq1cNPJxIYQElS5bBLHA94LOIY98yaL4PnOCAjnevPRs2IV5tP+eIhrfLt8bjsqpP 7G9F7MZkTmYjFNpIHDEe/Olo9584NX5PlQc9t2g6YwBzhB+n3+ShyraJinQP2nVN55 S7xZYUvVfUdKQ6hQO6WXejogF1ukoFuT8hMibMrE= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/94823] modulo arithmetic bug in random.tcc Date: Tue, 28 Apr 2020 22:36:00 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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: resolution bug_status 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: Tue, 28 Apr 2020 22:36:01 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94823 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Andrew Pinski --- Note there are two loops here where we could have an issue but .... In the first loop, it is ok usage because __k will be only 0 when the array will be filled with the same data (0x8b8b8b8bu) so that usage does not matt= er. The second loop is where it might matter but __k will never be 0 as __m is = will either be greater than or equal to __n.=