en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir#331145e6 [flang][NFC] Unify todo messagesThis patch is part of the upstreaming effort from fir-dev branch.Reviewed By: jeanPerierDifferential Revision: https://reviews.llvm.org/D128186Co-authored-by: Peter Steinfeld <psteinfeld@nvidia.com> List of files: /llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir Mon, 20 Jun 2022 13:43:44 +0000 Valentin Clement <clementval@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir#7ce8c6fc [Flang] Replace notifyMatchFailure with TODO hard failuresFor unimplemented patterns we revert to using TODO hard failures instead ofnotifyMatchFailure.For fir.select_type revert to using mlir::emiterror.For the fir.embox TODO on a type with len params we cannot add a test since the type cannot be converted to llvm.Adding negative tests using not and checking for the error message.TODO exits with an error in a build without assertion but aborts in abuild with assertions. Abort requires using not with the --crashoption. The two different usages of not is handled by using a customcommand %not_todo_cmd which is converted to not or not --crashdepending on the presence or absence of assertions. Using llvm-configto check the presence of assertions.Reviewed By: clementval, awarzynskiDifferential Revision: https://reviews.llvm.org/D114371 List of files: /llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir Wed, 01 Dec 2021 22:12:12 +0000 Kiran Chandramohan <kiran.chandramohan@arm.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir#46fd7fd7 [Flang] Replace notifyMatchFailure with TODO hard failuresFor unimplemented patterns we revert to using TODO hard failures instead ofnotifyMatchFailure.For fir.select_type revert to using mlir::emiterror.For the fir.embox TODO on a type with len params we cannot add a test since the type cannot be converted to llvm.Adding negative tests using not and checking for the error message.TODO exits with an error in a build without assertion but aborts in abuild with assertions. Abort requires using not with the --crashoption. The two different usages of not is handled by using a customcommand %not_todo_cmd which is converted to not or not --crashdepending on the presence or absence of assertions. Using llvm-configto check the presence of assertions.Reviewed By: clementval, awarzynskiDifferential Revision: https://reviews.llvm.org/D114371 List of files: /llvm-project-15.0.7/flang/test/Fir/Todo/dispatch_table.fir Wed, 01 Dec 2021 08:10:27 +0000 Kiran Chandramohan <kiran.chandramohan@arm.com>