Commit b49ee3d
committed
Replace printf with cout in JitCall tests
This hints towards a larger underlying problem in the driver when going through cling: On windows, the `stdout` buffer is not flushed. With gtest, all the printf statements in functions invoked with `JitCall` like:
`void f2(std::string &s) { std::cout << s.c_str(); };` appear at the end of the test suite run. Attempting to fix this issue by force flushing does not work, and printf statements in the test code itself appear on the screen. This indicates issues with linking, since the Interpreter runtime operating on a different buffer than the compile runtime. We ideally want to support the usage of printf statements when invoked through `JitCall`.1 parent b797dbb commit b49ee3d
1 file changed
+9
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
875 | 875 | | |
876 | 876 | | |
877 | 877 | | |
| 878 | + | |
| 879 | + | |
| 880 | + | |
| 881 | + | |
878 | 882 | | |
879 | 883 | | |
880 | | - | |
| 884 | + | |
| 885 | + | |
881 | 886 | | |
882 | 887 | | |
883 | 888 | | |
| |||
922 | 927 | | |
923 | 928 | | |
924 | 929 | | |
| 930 | + | |
925 | 931 | | |
926 | 932 | | |
927 | | - | |
928 | | - | |
| 933 | + | |
| 934 | + | |
929 | 935 | | |
930 | 936 | | |
931 | 937 | | |
| |||
0 commit comments