From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EC0473858C53; Mon, 31 Jul 2023 15:05:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC0473858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1690815956; bh=k/r/+BVl4tlAR74UmfGyT/4Uvy6ojeev+U5xQOswBws=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZEW4Zvde7PZykhcmxRJjav4W684SjxhQr6KfiyC49aNtLxfT+c2QLEBXjDLGP60K4 4nHo0cnWx8uMx14G6xFpyzh6v77FpdfSKhkUk+Vq4Kn2kFm5RenzlXIEBCEJXQiztp u528ToyxrmwN/BU2YC0k9pJasNNPtYCJKOXLZgus= From: "headch at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110861] Bad codegen leading to runtime segfault when mixing import and #include Date: Mon, 31 Jul 2023 15:05:56 +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.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: headch at gmail 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: 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=3D110861 --- Comment #1 from Christopher Head --- Note that I ran into this while trying to find a small repro case for the s= ame symptoms (uninitialized =E2=80=9Cthis=E2=80=9D and segfault using a string_= view) in a larger project, where I originally saw the same thing happen while only importing stdlib headers, not including any of them, and eventually made this as a smaller example.=