Date: Sat, 18 Jun 2022 23:36:43 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 264730] clang++ -fmodules fails when using stdout from cstdio: error: declaration of '__stdoutp' must be imported from module 'std.iosfwd' before it is required Message-ID: <bug-264730-29464-JgigGtFE5s@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264730-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-264730-29464@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264730 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> --- As I understand it, the C++20 standard makes a distinction between: A) C++ headers ( such as <chrono> ) vs. B) C headers adopted by C++ ( such as <cassert> or <cstdio> ) So that: export module NAME0; import <chrono> . . . is supposed to be known to be okay. But: export module NAME1; import <cstdio> . . . is not portable and could give an error as a result without violating the standard. It leaves me wondering if the specific example presented has wondered outside what is actually supposed to be guaranteed by the C++20 standard. (At this point I do not know.) The context is different in the example but it might be related. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264730-29464-JgigGtFE5s>