This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
- From: "Yufeng Zhang" <Yufeng dot Zhang at arm dot com>
- To: "'Mark Mitchell'" <mark at codesourcery dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>, <jason at redhat dot com>
- Date: Fri, 25 Feb 2011 16:14:38 -0000
- Subject: RE: [PING^2] [PR46003, C++] Fix the assertion failure in build_target_expr
- References: <000401cbd209$c85e6840$591b38c0$@Zhang@arm.com> <4D63348A.8070802@codesourcery.com>
On 2/22/2011 03:59 AM, Mark Mitchell wrote:
>
>> http://gcc.gnu.org/ml/gcc-patches/2011-02/msg00689.html
>
>> Any comment will be appreciated.
>
> I would think that when we call the constructor on ARM we should cast
> the result to "void". Then we would presumably not have to change
> build_aggr_init_expr. Does that work?
Do you mean casting the result of _all_ constructor calls on ARM to
"void" or just for that particular case? I'm not sure whether this
works or whether this will introduce any inconsistency.
I wonder if there is any particular concern about changing
build_aggr_init_expr, or any reason that it's not necessary for the
'is_ctor' to consider overloaded constructor calls.
Many thanks,
Yufeng