Hi! This commits are changed and improved by the following commits: bcheck for windows and bcheck support for ARCH=x86_64. But there is a trick to force a bcheck.o linking: compiling a dummy program with the local array. Otherwise bcheck.o may be not linked. I don't know a way to force linking bcheck.o if a main program is a dummy one (do not contain a local array):
int main(void) { // int v[10]; // when this is present then bcheck.o is linked from a library // otherwise not return 0; } PS: a __bcheck_init function is not called from ".init" section on windows for unknown reason. 2015-04-11 14:13 GMT+03:00, Thomas Preud'homme <robo...@celest.fr>: > Le mercredi 25 mars 2015, 20:59:23 Sergey Korshunoff a écrit : >> Hi! There is a patch attached. This patch: >> 1) installs bcheck.o along with the libtcc1.a >> 2) enforces bcheck.o linking > > I just tested your patch without the tcc_add_support(s1, "bcheck.o"); and it > > works fine for me. This is not really surprising since as I said earlier > bcheck.o is part of libtcc1.a which is linked. > > So can you revert this commit (except the if (!sym_index) part) and the > following commit 548a55eda53a0dcf2eabd617115c4e46330d7e23 ? If you did > observe > an issue without this, please tell me how to reproduce it and I'll look what > > is the actual issue. > > Note that I do appreciate all your efforts to improve TinyCC, I don't want > you > to think the contrary. ;-) > > Thanks in advance. > > Best regards, > > Thomas _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel