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 C90C1383907F; Mon,  5 Jun 2023 13:44:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C90C1383907F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685972652;
	bh=S1N5+jX70Bl7JwibItkD8GBAzTXzVXJmD+GDPcEjgkg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Q1m+qw3/q0ArAVOa8yVus7mWzr/nY490N5zE/Zgl04x54/alQnpkobpNy3NfeaPSh
	 YYItza9t8kZOdzuPoX8JtQ7zuYvFj3z9jr7FiRHT0J0GYPmsdrBlM4gOUqf2RnmHyy
	 evYkxZjPwVGOURkj6+N9K/4L/je8mlW1qnd1yN7I=
From: "markmigm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103499] C++20 modules error: invalid use of non-static
 member function
Date: Mon, 05 Jun 2023 13:44:11 +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: 11.2.0
X-Bugzilla-Keywords: ice-checking, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: markmigm at gmail dot com
X-Bugzilla-Status: NEW
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-103499-4-ckv4LfhPr5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103499-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=3D103499

--- Comment #6 from Mark Millard <markmigm at gmail dot com> ---
(In reply to Jonathan Wakely from comment #5)

The relationship I was thinking of was that, without this
being fixed, the full set of header units for the standard
library probably could not be completed: a blocking issue
relative to completing "header-units of STL header files".
(Likely necessary but not sufficient for such completion.)

I was not trying to say that the issue was limited to just
"header-units of STL header files".

As long as the problem is fixed, the relationship would
be handled, just more implicitly relative to the
completion of the "header-units of STL header files".

It is good to have examples that do not involve materials
from /usr/include/c++/ , for sure.=