public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103600] Cannot use typeid result in constant expressions
Date: Thu, 03 Nov 2022 13:29:06 +0000	[thread overview]
Message-ID: <bug-103600-4-jGDpHiy01o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103600-4@http.gcc.gnu.org/bugzilla/>

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

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppalka at gcc dot gnu.org
             Status|ASSIGNED                    |RESOLVED
   Target Milestone|---                         |12.0
         Resolution|---                         |FIXED

--- Comment #11 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Thus fixed since GCC 12

      parent reply	other threads:[~2022-11-03 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  9:38 [Bug c++/103600] New: " redi at gcc dot gnu.org
2021-12-07  9:51 ` [Bug c++/103600] " pinskia at gcc dot gnu.org
2021-12-07  9:52 ` pinskia at gcc dot gnu.org
2021-12-07 10:01 ` redi at gcc dot gnu.org
2021-12-07 13:23 ` jakub at gcc dot gnu.org
2021-12-07 13:47 ` redi at gcc dot gnu.org
2021-12-07 16:44 ` jakub at gcc dot gnu.org
2021-12-08  0:30 ` redi at gcc dot gnu.org
2022-01-03 10:24 ` cvs-commit at gcc dot gnu.org
2022-01-03 10:34 ` jakub at gcc dot gnu.org
2022-01-06 14:49 ` ppalka at gcc dot gnu.org
2022-11-03 13:29 ` ppalka at gcc dot gnu.org [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=bug-103600-4-jGDpHiy01o@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).