aboutsummaryrefslogtreecommitdiff
path: root/gotools/go.1
diff options
context:
space:
mode:
authorAndrew Pinski <pinskia@gmail.com>2023-10-20 14:49:32 -0700
committerAndrew Pinski <pinskia@gmail.com>2023-10-23 03:55:15 -0700
commit85e930ac8557c444680b5b29a0a13a14ea6672b5 (patch)
tree97967a1e70c9d6b6e49b5c24faeabe1a1c696a7a /gotools/go.1
parent13c0d052478bb45cc97869f5cc333f269aadb36f (diff)
downloadgcc-85e930ac8557c444680b5b29a0a13a14ea6672b5.zip
gcc-85e930ac8557c444680b5b29a0a13a14ea6672b5.tar.gz
gcc-85e930ac8557c444680b5b29a0a13a14ea6672b5.tar.bz2
Use error_mark_node after error in convert
While working on PR c/111903, I Noticed that convert will convert integer_zero_node to that type after an error instead of returning error_mark_node. From what I can tell this was the old way of not having error recovery since other places in this file does return error_mark_node and the places I am replacing date from when the file was imported into the repro (either via a gcc2 merge or earlier). I also had to update the objc front-end to allow for the error_mark_node change, I suspect you could hit the ICE without this change though. Bootstrapped and tested on x86_64-linux-gnu with no regressions. gcc/ChangeLog: * convert.cc (convert_to_pointer_1): Return error_mark_node after an error. (convert_to_real_1): Likewise. (convert_to_integer_1): Likewise. (convert_to_complex_1): Likewise. gcc/objc/ChangeLog: * objc-gnu-runtime-abi-01.cc (build_objc_method_call): Allow for error_operand after call to build_c_cast. * objc-next-runtime-abi-01.cc (build_objc_method_call): Likewise. * objc-next-runtime-abi-02.cc (build_v2_build_objc_method_call): Likewise.
Diffstat (limited to 'gotools/go.1')
0 files changed, 0 insertions, 0 deletions