From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 3E76A385803B; Wed,  3 Jan 2024 09:59:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E76A385803B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704275991;
	bh=pm7Juy52mNNZm1oY7a/nfWFGVumrBDLya28UXScNAXk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pInN1+8YIiZFpf4yLoiE0WWxLEIcGzX+c2wfMzf6EnUbhdwje185Sc2rAfh7HbNHs
	 6hzOPai7xxbPj6YTlucXXc41Vrp6QFkePORuVidqm+H3TYzbzpP1fd9UMonMXgXCc0
	 BsIPbDzlrgWnO3RXFgrhsujXDyaGxErS8pgKAqqg=
From: "carsten.schmidt-achim at gmx dot de" <gcc-bugzilla@gcc.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 09:59:49 +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: carsten.schmidt-achim at gmx dot de
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: <bug-113202-4-dClRFzmOIz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113202-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113202-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113202

--- Comment #6 from Carsten Schmidt <carsten.schmidt-achim at gmx dot de> -=
--
> Why do you think this is a bug?

1. Considering the "possible implementation" of cppreference.com, pointer
   arithmetic, e.g. ptr-ptr, should not be an issue when searching for the
   sentinel.

2. Using ranges::find() does not show the observed behavior.

3. Other implementations of the libstdc++, e.g. MSVC, work properly.=