From: Gavin Ray <ray.gavin97@gmail.com>
To: libstdc++@gcc.gnu.org
Subject: Bug in <complex> header in trunk from malformed "requires" statement, causes compilation errors if included
Date: Fri, 18 Nov 2022 13:59:13 -0500 [thread overview]
Message-ID: <CAFtvWZM07WNyawZ7-7LNDjsEb0rmF3ra2F-N+y26trsAjQ7cJQ@mail.gmail.com> (raw)
Hello all,
Hit a very confusing bug this morning. I'm using Clang with GCC
upstream libstdc++ from jwakely's repo.
The following program fails to compile:
#include <complex>
int main() { return 0; }
It appears there was an initial commit which added "requires" clauses,
and then a fixup commit later:
- libstdc++: Fix up <complex> for extended floating point types
[PR107649] · gcc-mirror/gcc@0e2c551 (github.com)
But there seems to be one last malformed "requires" statement in trunk:
https://github.com/gcc-mirror/gcc/blob/59cc4da605e5cb8e31e9f1d54ef2b5ba47fc8f88/libstdc%2B%2B-v3/include/std/complex#L2531
(Big thanks to Luke D'Alessandro for figuring this all out)
Thought I'd let you folks know.
Thank you!
next reply other threads:[~2022-11-18 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:59 Gavin Ray [this message]
2022-11-18 21:14 ` Jonathan Wakely
2022-11-19 15:09 ` Jonathan Wakely
2022-11-19 15:19 ` Gavin Ray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFtvWZM07WNyawZ7-7LNDjsEb0rmF3ra2F-N+y26trsAjQ7cJQ@mail.gmail.com \
--to=ray.gavin97@gmail.com \
--cc=libstdc++@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).