public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/rust/master] Merge #1394 Date: Tue, 19 Jul 2022 21:57:52 +0000 (GMT) [thread overview] Message-ID: <20220719215752.BA2A5385829A@sourceware.org> (raw) https://gcc.gnu.org/g:1b5676645a52f46de0011b9434f76c249fbb8d81 commit 1b5676645a52f46de0011b9434f76c249fbb8d81 Merge: 6622ae2cd0a fb1b2a6bf5e Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com> Date: Tue Jul 19 10:32:55 2022 +0000 Merge #1394 1394: Fix parsing grammer of grouped expressions as the block tail expression r=philberty a=philberty When we want to compile a grouped expression we had a check for the LEFT_PAREN during the parse_expr_without_block but this can't be handled here since in this paticular example the grouped expressions is simply the lhs of the bit shift expression. This is already handled as part of parse_expr so we can simply remove the rule here and rely on parse_expr handling this. Fixes #1393 Co-authored-by: Philip Herron <philip.herron@embecosm.com> Diff: gcc/rust/parse/rust-parse-impl.h | 6 ------ gcc/testsuite/rust/compile/issue-1393.rs | 13 +++++++++++++ 2 files changed, 13 insertions(+), 6 deletions(-)
reply other threads:[~2022-07-19 21:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220719215752.BA2A5385829A@sourceware.org \ --to=tschwinge@gcc.gnu.org \ --cc=gcc-cvs@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).