public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105732] [REGRESSION] internal compiler error: unspellable token PADDING Date: Wed, 25 May 2022 22:38:39 +0000 [thread overview] Message-ID: <bug-105732-4-p6xvXnd58P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105732-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105732 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. Reduced as much as I could: #define _VA_FEATURE_DETECT__3RD_ARG(_placeholder_1, _placeholder_2, value, ...) value # define _VA_FEATURE_OPT_DISAPPEARS 1 # define _VA_FEATURE_OPT_DISAPPEARS__VA_OPT__(_placeholder) 0 # define _VA_FEATURE_OPT_DETECT_UNEXPANDED(...) _VA_FEATURE_OPT_DISAPPEARS##__VA_OPT__(foo) # define _VA_FEATURE_OPT_DETECT_VERIFY_2_ARGS_TEST_ZERO(_placeholder_1, _placeholder_2) \ _VA_FEATURE_OPT_DETECT_UNEXPANDED() # define _VA_FEATURE_OPT_DETECT_1_OR_2_ARGS(_placeholder, ...) \ _VA_FEATURE_DETECT__3RD_ARG(__VA_ARGS__, \ _VA_FEATURE_OPT_DETECT_VERIFY_2_ARGS_TEST_ZERO, \ 0) # define _VA_FEATURE_OPT_DETECT_1_ARG(...) \ _VA_FEATURE_OPT_DETECT_1_OR_2_ARGS(bar, __VA_OPT__(, ))(__VA_OPT__(, )) # define _VA_FEATURE_OPT_DETECT_SUPPORTED _VA_FEATURE_OPT_DETECT_1_ARG(?) # if _VA_FEATURE_OPT_DETECT_SUPPORTED # endif
next prev parent reply other threads:[~2022-05-25 22:38 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-25 22:29 [Bug c++/105732] New: " linux_dr at yahoo dot com 2022-05-25 22:30 ` [Bug c++/105732] " linux_dr at yahoo dot com 2022-05-25 22:35 ` linux_dr at yahoo dot com 2022-05-25 22:38 ` pinskia at gcc dot gnu.org [this message] 2022-05-25 22:39 ` [Bug preprocessor/105732] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-05-25 22:49 ` linux_dr at yahoo dot com 2022-05-25 22:53 ` mpolacek at gcc dot gnu.org 2022-05-25 22:54 ` linux_dr at yahoo dot com 2022-05-25 23:05 ` pinskia at gcc dot gnu.org 2022-05-25 23:06 ` [Bug preprocessor/105732] [9/10/11/12/13 " pinskia at gcc dot gnu.org 2022-05-25 23:44 ` mpolacek at gcc dot gnu.org 2022-05-26 13:38 ` jakub at gcc dot gnu.org 2022-05-26 14:12 ` jakub at gcc dot gnu.org 2022-05-27 6:26 ` rguenth at gcc dot gnu.org 2022-05-27 7:18 ` [Bug preprocessor/105732] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-05-28 6:19 ` herrtimson at yahoo dot de 2022-05-28 6:34 ` jakub at gcc dot gnu.org 2022-05-29 15:13 ` linux_dr at yahoo dot com 2022-05-29 19:58 ` cvs-commit at gcc dot gnu.org 2022-05-30 3:37 ` cvs-commit at gcc dot gnu.org 2022-05-30 7:58 ` [Bug preprocessor/105732] [10/11 " jakub at gcc dot gnu.org 2022-06-10 17:28 ` linux_dr at yahoo dot com 2022-06-10 17:44 ` jakub at gcc dot gnu.org 2022-06-12 2:17 ` linux_dr at yahoo dot com 2022-06-15 12:02 ` cvs-commit at gcc dot gnu.org 2022-06-15 12:06 ` cvs-commit at gcc dot gnu.org 2022-06-15 12:08 ` jakub at gcc dot gnu.org 2023-03-26 15:59 ` jakub 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-105732-4-p6xvXnd58P@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: linkBe 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).