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 7B63F3858C54; Wed, 26 Apr 2023 16:56:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B63F3858C54
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1682528160;
	bh=pGeLz6RiIhuYb3yTkwmylobgbYHU8Jk07vt8yxwfjfg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=U7XGF72hTVULALDLjpqyQEWUm4rHMDzAlW38/YqWu0kd2fPMtb14xDNz3uq6yNgoN
	 WccmMUsU8c1BAXdLTLjrAcF8ekD6rYYdogvzCWliTBAXDYQpCOtYU5cvtX+xH0H6b6
	 mj0rE7o8fCnjDE9qGS+CsIiuR+9JmA/OkupOeGb8=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109633] segfault using cout after set with simple prog from
 cppreference.com
Date: Wed, 26 Apr 2023 16:56:00 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: 
Message-ID: <bug-109633-4-IoafuGYqsd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109633-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109633-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=3D109633

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Since I see this as going to be a FAQ soon, I submitted a patch to add a no=
te
to the begining of changes page for GCC 13:
https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616806.html=