public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Alex Hornby <ahornby@fb.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: New g++ folly compile error with gcc 11.x. Bisected to PR99445 c++: Alias template in pack expansion
Date: Thu, 13 Jan 2022 17:29:38 +0000	[thread overview]
Message-ID: <CAH6eHdRDkBNNb_e5o723m=mVo4cy3HEUMyfx8_=Adjb4=6t0PA@mail.gmail.com> (raw)
In-Reply-To: <E57945D2-3414-4682-97C3-4A21815BC03D@fb.com>

On Thu, 13 Jan 2022 at 14:25, Alex Hornby <ahornby@fb.com> wrote:
>
> On 1/13/22, 12:36 PM, "Jonathan Wakely" <jwakely.gcc@gmail.com> wrote:
>
>     >On Thu, 13 Jan 2022 at 11:46, Alex Hornby via Gcc-help
>     <gcc-help@gcc.gnu.org> wrote:
>     >>
>     >> When compiling folly on Fedora 35 with gcc from the included 11.2.1-7 package, I found that the badge_test code fails to compile,  whereas it builds fine with gcc 10.x and with the fedora 35 clang (13.0.0-3.fc35)).
>     >>
>     >> Bisecting from https://gcc.gnu.org/git/gcc.git  with pre-processed source indicates problem introduced in commit: [a2531859bf5bf6cf1f29c0dca85fd26e80904a5d] c++: Alias template in pack expansion [PR99445]
>
>     > Please report this to Bugzilla, thanks.
>
> Done:  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104008

Great, thanks. I just noticed PR 102869 which might be the same issue.

      reply	other threads:[~2022-01-13 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 11:45 Alex Hornby
2022-01-13 12:36 ` Jonathan Wakely
2022-01-13 14:25   ` Alex Hornby
2022-01-13 17:29     ` Jonathan Wakely [this message]

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='CAH6eHdRDkBNNb_e5o723m=mVo4cy3HEUMyfx8_=Adjb4=6t0PA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=ahornby@fb.com \
    --cc=gcc-help@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).