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 #1466
Date: Sat, 13 Aug 2022 08:42:45 +0000 (GMT)	[thread overview]
Message-ID: <20220813084245.2F6B63858415@sourceware.org> (raw)

https://gcc.gnu.org/g:fadc70475147768a68ccc9e0011bd3fe85d90096

commit fadc70475147768a68ccc9e0011bd3fe85d90096
Merge: 3399688a1bf 9caea7bcf80
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Aug 12 11:40:14 2022 +0000

    Merge #1466
    
    1466: Dont return error_mark_node on bad CallExpr arguments r=philberty a=philberty
    
    If we return error_mark_node on a bad expression argument we loss alot of
    useful debug info from the error node within the -fdump-tree-original which
    saves alot of debug printf.
    
    
    Co-authored-by: Philip Herron <philip.herron@embecosm.com>

Diff:

 gcc/rust/rust-gcc.cc | 2 --
 1 file changed, 2 deletions(-)


                 reply	other threads:[~2022-08-13  8:42 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=20220813084245.2F6B63858415@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).