public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/105732] [10/11 Regression] internal compiler error: unspellable token PADDING Date: Wed, 15 Jun 2022 12:02:34 +0000 [thread overview] Message-ID: <bug-105732-4-BoV3g5g2Oc@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 #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:49e320ac0792672e2137ca47215fd7f935302895 commit r11-10072-g49e320ac0792672e2137ca47215fd7f935302895 Author: Jakub Jelinek <jakub@redhat.com> Date: Sun May 29 21:57:51 2022 +0200 libcpp: Ignore CPP_PADDING tokens in _cpp_parse_expr [PR105732] The first part of the following testcase (m1-m3 macros and its use) regressed with my PR89971 fix, but as the m1,m4-m5 and its use part shows, the problem isn't new, we can emit a CPP_PADDING token to avoid it from being adjacent to whatever comes after the __VA_OPT__ (in this case there is nothing afterwards, true). In most cases these CPP_PADDING tokens don't matter, all other callers of cpp_get_token_with_location either ignore CPP_PADDING tokens completely (e.g. c_lex_with_flags) or they just remember them and take them into account when printing stuff whether there should be added whitespace or not (scan_translation_unit + token_streamer::stream). So, I think we should just ignore CPP_PADDING tokens the same way in _cpp_parse_expr. 2022-05-27 Jakub Jelinek <jakub@redhat.com> PR preprocessor/105732 * expr.c (_cpp_parse_expr): Handle CPP_PADDING by just another token. * c-c++-common/cpp/va-opt-10.c: New test. (cherry picked from commit 58a40e76ebadce78639644cd3d56e42b68336927)
next prev parent reply other threads:[~2022-06-15 12:02 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-25 22:29 [Bug c++/105732] New: [REGRESSION] " 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 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 [this message] 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-BoV3g5g2Oc@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).