Re: [PATCH 1/2] RFC: C++: attempt to provide location_t in more places

2015-11-25 Thread Jason Merrill
It's not clear to me whether I should be passing in UNKNOWN_LOCATION or input_location to the various functions. cp_build_unary_op used input_location in various places internally, so I've passed that in wherever there isn't a better value. Rather than try to get this right now I'm inclined to

[PATCH 1/2] RFC: C++: attempt to provide location_t in more places

2015-11-25 Thread David Malcolm
This patch avoids the need for calls to protected_set_expr_location in the followup patch by adding location_t params to the following functions: - build_new - cp_build_indirect_ref - cp_build_unary_op - cp_build_c_cast - cp_build_modify_expr It's not clear to me whether I should be pass