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 #1574
Date: Wed, 12 Oct 2022 10:14:49 +0000 (GMT)	[thread overview]
Message-ID: <20221012101449.ABD88384F029@sourceware.org> (raw)

https://gcc.gnu.org/g:3e7320510e7bb774295ecbd8089a9f51d6475959

commit 3e7320510e7bb774295ecbd8089a9f51d6475959
Merge: 06fe912b70b d4c07a9b47c
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Mon Oct 10 16:46:57 2022 +0000

    Merge #1574
    
    1574: fix ICE on missing closing paren r=dkm a=dkm
    
    Fix crash (segfault) on a missing closing parenthesis when parsing the expressions in a block. The returned `expr` was missing a check before being used.
    
    Add corresponding test.
    
    Signed-off-by: Marc Poulhiès <dkm@kataplop.net>
    
    Co-authored-by: Marc Poulhiès <dkm@kataplop.net>

Diff:

 gcc/rust/parse/rust-parse-impl.h                    | 15 +++++++++++----
 gcc/testsuite/rust/compile/missing_closing_paren.rs |  3 +++
 2 files changed, 14 insertions(+), 4 deletions(-)

                 reply	other threads:[~2022-10-12 10:14 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=20221012101449.ABD88384F029@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: 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).