public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gavin Ray <ray.gavin97@gmail.com>
Cc: libstdc++@gcc.gnu.org
Subject: Re: Bug in <complex> header in trunk from malformed "requires" statement, causes compilation errors if included
Date: Fri, 18 Nov 2022 21:14:13 +0000	[thread overview]
Message-ID: <CAH6eHdRU+b8a1UpZpBtaRC=eCdNxtrK=ZTTUs7_KXY3_-3nhDw@mail.gmail.com> (raw)
In-Reply-To: <CAFtvWZM07WNyawZ7-7LNDjsEb0rmF3ra2F-N+y26trsAjQ7cJQ@mail.gmail.com>

On Fri, 18 Nov 2022 at 18:59, Gavin Ray via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> 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)

Yes, that was https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649 but
isn't included in my gcc-latest builds yet.

>
> 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

Thanks.

  reply	other threads:[~2022-11-18 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 18:59 Gavin Ray
2022-11-18 21:14 ` Jonathan Wakely [this message]
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='CAH6eHdRU+b8a1UpZpBtaRC=eCdNxtrK=ZTTUs7_KXY3_-3nhDw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ray.gavin97@gmail.com \
    /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).