public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104008] [11/12 Regression] New g++ folly compile error with gcc 11.x. Bisected to PR99445 c++: Alias template in pack expansion
Date: Thu, 13 Jan 2022 14:55:13 +0000	[thread overview]
Message-ID: <bug-104008-4-5ayol9R6lJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104008-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104008

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |jason at gcc dot gnu.org
   Target Milestone|---                         |11.3
            Summary|New g++ folly compile error |[11/12 Regression] New g++
                   |with gcc 11.x. Bisected to  |folly compile error with
                   |PR99445 c++: Alias template |gcc 11.x. Bisected to
                   |in pack expansion           |PR99445 c++: Alias template
                   |                            |in pack expansion

  reply	other threads:[~2022-01-13 14:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 14:20 [Bug c++/104008] New: " ahornby at fb dot com
2022-01-13 14:55 ` jakub at gcc dot gnu.org [this message]
2022-01-13 17:28 ` [Bug c++/104008] [11/12 Regression] " redi at gcc dot gnu.org
2022-02-01 15:59 ` marxin at gcc dot gnu.org
2022-02-05 12:28 ` ahornby at fb dot com
2022-02-05 12:32 ` ahornby at fb dot com
2022-02-05 12:33 ` ahornby at fb dot com
2022-02-14 17:39 ` alex_700_95 at mail dot ru
2022-02-22 10:03 ` [Bug c++/104008] [11/12 Regression] New g++ folly compile error since r11-7931-ga2531859bf5bf6cf marxin at gcc dot gnu.org
2022-03-11 22:49 ` mpolacek at gcc dot gnu.org
2022-03-14 23:53 ` mpolacek at gcc dot gnu.org
2022-03-18 16:50 ` cvs-commit at gcc dot gnu.org
2022-03-18 16:51 ` [Bug c++/104008] [11 " mpolacek at gcc dot gnu.org
2022-03-18 18:58 ` ppalka at gcc dot gnu.org
2022-03-18 19:40 ` mpolacek at gcc dot gnu.org
2022-03-21 19:40 ` mpolacek at gcc dot gnu.org
2022-03-28 15:04 ` cvs-commit at gcc dot gnu.org
2022-04-12 20:14 ` cvs-commit at gcc dot gnu.org
2022-04-12 20:24 ` jason at gcc dot gnu.org

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=bug-104008-4-5ayol9R6lJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).