This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr

From: Jason Merrill <jason at redhat dot com>
To: Yufeng Zhang <Yufeng dot Zhang at arm dot com>
Cc: gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com
Date: Sat, 26 Feb 2011 12:38:03 -0500
Subject: Re: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
References: <000401cbd209$c85e6840$591b38c0$@Zhang@arm.com> <4D645152.4060902@redhat.com> <000501cbd506$c4a09750$4de1c5f0$@Zhang@arm.com>

On 02/25/2011 11:12 AM, Yufeng Zhang wrote:

So this is how we get into build_target_expr without the overload
resolution performed. Is it an expected behaviour?

Thanks for the analysis. We shouldn't be calling build_aggr_init_expr for such a CALL_EXPR. The problem seems to be with the calls to build_cplus_new in convert_like_real, which seem to be redundant; we should have already called from build_cxx_call when we built up the call in the first place. What happens if we just remove all those calls?

Jason

References:
- [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
  - From: Yufeng Zhang
- Re: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
  - From: Jason Merrill
- RE: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
  - From: Yufeng Zhang

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]