procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

init.c (build_new_1): Use cp_build_function_call_nary instead of cp_build_function_call.

Browse source 
* init.c (build_new_1): Use cp_build_function_call_nary instead of
	cp_build_function_call.

From-SVN: r162241
This commit is contained in:
Nathan Froyd 2010-07-16 02:37:10 +00:00 • committed by Nathan Froyd
parent 71008de4b3
commit 6998c7ede7
2 changed files with 7 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/cp/ChangeLog
View file

@ -1,3 +1,8 @@
2010-07-15 Nathan Froyd <froydnj@codesourcery.com>
* init.c (build_new_1): Use cp_build_function_call_nary instead of
cp_build_function_call.
2010-07-15 Jason Merrill <jason@redhat.com>
PR c++/44909

6
gcc/cp/init.c
View file

@ -2033,10 +2033,8 @@ build_new_1 (VEC(tree,gc) **placement, tree type, tree nelts,
}
alloc_fn = OVL_CURRENT (alloc_fn);
class_addr = build1 (ADDR_EXPR, jclass_node, class_decl);
alloc_call = (cp_build_function_call
(alloc_fn,
build_tree_list (NULL_TREE, class_addr),
complain));
alloc_call = cp_build_function_call_nary (alloc_fn, complain,
class_addr, NULL_TREE);
}
else if (TYPE_FOR_JAVA (elt_type) && MAYBE_CLASS_TYPE_P (elt_type))
{