From 9caea7bcf8026972544ef7aae26a8df1a8bf8db1 Mon Sep 17 00:00:00 2001
From: Philip Herron <philip.herron@embecosm.com>
Date: Thu, 11 Aug 2022 15:50:12 +0100
Subject: Dont return error_mark_node on bad CallExpr arguments

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.
---
 gcc/rust/rust-gcc.cc | 2 --
 1 file changed, 2 deletions(-)

(limited to 'gcc')

diff --git a/gcc/rust/rust-gcc.cc b/gcc/rust/rust-gcc.cc
index c8eee0f..c172917 100644
--- a/gcc/rust/rust-gcc.cc
+++ b/gcc/rust/rust-gcc.cc
@@ -1778,8 +1778,6 @@ Gcc_backend::call_expression (tree fn, const std::vector<tree> &fn_args,
   for (size_t i = 0; i < nargs; ++i)
     {
       args[i] = fn_args.at (i);
-      if (args[i] == error_mark_node)
-	return error_mark_node;
     }
 
   tree fndecl = fn;
-- 
cgit v1.1