public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vittorio.romeo at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100157] Support `__type_pack_element` like Clang
Date: Thu, 30 Jun 2022 12:46:40 +0000	[thread overview]
Message-ID: <bug-100157-4-CJVZ4DfYCE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100157-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Vittorio Romeo <vittorio.romeo at outlook dot com> ---
Thank you, Jonathan, for looking into this. I feel like it might be worthwhile
to keep the same name as Clang for compatibility, or maybe talk to some Clang
developers and see if there can be an agreement on naming and design that works
for both compilers -- would be nice to have something that works for both GCC
and Clang in the same way.

  parent reply	other threads:[~2022-06-30 12:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 17:44 [Bug c++/100157] New: " vittorio.romeo at outlook dot com
2021-04-21  6:21 ` [Bug c++/100157] " rguenth at gcc dot gnu.org
2022-06-29 23:27 ` redi at gcc dot gnu.org
2022-06-29 23:33 ` redi at gcc dot gnu.org
2022-06-29 23:38 ` redi at gcc dot gnu.org
2022-06-30 10:39 ` m.cencora at gmail dot com
2022-06-30 11:11 ` redi at gcc dot gnu.org
2022-06-30 11:19 ` redi at gcc dot gnu.org
2022-06-30 11:44 ` m.cencora at gmail dot com
2022-06-30 12:46 ` vittorio.romeo at outlook dot com [this message]
2022-06-30 13:05 ` redi at gcc dot gnu.org
2022-06-30 13:08 ` redi at gcc dot gnu.org
2022-06-30 13:09 ` vittorio.romeo at outlook dot com
2022-06-30 13:14 ` redi at gcc dot gnu.org
2022-11-29 15:28 ` pdimov at gmail dot com
2023-04-19 19:37 ` cvs-commit at gcc dot gnu.org
2023-04-26  6:55 ` rguenth at gcc dot gnu.org
2023-04-26  8:08 ` redi 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-100157-4-CJVZ4DfYCE@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).