On 03/02/2018 11:25 AM, Jakub Jelinek wrote:
Various spots in the FE don't really like if error_mark_node is deeply
embedded in expression operands, in this case tsubst_copy_and_build
creates CONVERT_EXPR <some_type, error_mark_node> on which
Fixed by just returning error_mark_node (various other spots in
tsubst_copy_and_build do the same).
While at it, I've discovered 3 spots in the function which were using
return instead of RETURN and thus wouldn't properly restore input_location;
I wonder if eventually this shouldn't be done through some sentinel class
where the destructor would restore input_location and just use return
instead of RETURN.
Anyway, bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?