From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 97D4C3858D28; Wed, 3 Jan 2024 10:20:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 97D4C3858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704277222; bh=wCuc41+sRMZ4VICBrO1axqxEmmaarvncUmZpk2Mx8/I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=LaF9A6+dseQc8bYSHcEwi0JGkcAl//aHSUCB4+QO5ShjEnF1uQthaMZydNbZ7BRVN 33Ooq6nLoZlrm2ArTMdq6yx+lLQMhUU4lwVtl00ScUwebuFFM8/w455r9Usp5t4i3Y xIfA58Z1qioqRh2ysfu6BaUB6pZ4rxBvBX5dNlbs= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113202] std::find does not work with the maximum range of pointers Date: Wed, 03 Jan 2024 10:20:21 +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: 13.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: cc 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113202 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #10 from Xi Ruoyao --- And "possible implementation" is just one of the infinite allowed implementations. libstdc++ can use a different implementation for speed/simplicity/whatever as long as it does not violate the standard.=