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 4D80C3858C54; Mon, 27 Mar 2023 19:34:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4D80C3858C54
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1679945642;
	bh=I7P1q9+eGMGlHhtL24iDARRhMDXJUbXHxqx6TMHov2Q=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=dP54p7Hhafht6tuaLk0v6FGK1d67P0Fa36aRKmDNlwz5Md4zsZOplWvsxYNgfxnmo
	 EW/mR+0Jsh0k6egtonA5Lunz8rKWqcuCS1oQk/sxK4NYQqcFrMEwJdIIIaC5imXG1w
	 fzBvzJeC3aQYXkrdk4hsCmNOm9dP8xHB7nt6w/cA=
From: "pmorf at apple dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/109306] The strstr implementation in libiberty might have
 undefined behavior (out of bounds mem access)
Date: Mon, 27 Mar 2023 19:34:02 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pmorf at apple 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: <bug-109306-4-BFErHE3eW6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109306-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=3D109306

--- Comment #2 from pmorf at apple dot com ---
Oh. Is there a different implementation I'll link against when telling gcc =
to
use the c++11 standard ?=