Re: [Tinycc-devel] Some fixes for x86_64 and general code to enable compiling GCC
Michael Matz wrote: Hi, I was bored the last weekend and stumbled over tinycc, tried compiling GCC with it, which breaks in multiple ways, sometimes not parsing stuff, sometimes miscompiling it, and thought about hacking some other compiler than GCC :) I just pushed nine patches to mob to fix all the problems I encountered (also attached for reference). Thanks for sharing this moment of productive boredom. I've added testcases for all the issues to tcctest.c. I can now build current GCC (well, r186469 plus a modification, see below) with tinycc on x86_64 (all language frontends written in C, i.e. c, c++, objc, objc++ and fortran), and that so built GCC is able to compile all its own target libraries. If practicable, could you post the recipe that you used to build GCC with TCC? (If it is a script you might just push it into our 'tests' directory. There is already gcctestsuite.sh) The nice thing is that I even found a real bug in GCC (fixing it is required to make it work with tinycc on x86_64), which I'm going to apply upstream later, but for completeness I attach it here too in case anyone wants to play with it right now (fix-diag-vaend.diff) :) Have fun, Michael. It was fun to read, indeed. --- grischka ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Fwd: Use CString to concat linker options
Thomas Preud'homme wrote: About the cstr_*, are they now part of the library on Windows? I mean if they are exported some people might start to use them, no? Same thing with pstrcat or tcc_realloc as in your original patch. As to some people they hopefully know the meaning of 'undocumented feature'. --- grischka ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] Some fixes for x86_64 and general code to enable compiling GCC
Hi, On Sat, 21 Apr 2012, grischka wrote: I can now build current GCC (well, r186469 plus a modification, see below) with tinycc on x86_64 (all language frontends written in C, i.e. c, c++, objc, objc++ and fortran), and that so built GCC is able to compile all its own target libraries. If practicable, could you post the recipe that you used to build GCC with TCC? (If it is a script you might just push it into our 'tests' directory. There is already gcctestsuite.sh) No script. Just: from directory in which `pwd`/gcc is the top-level dir of checked out gcc: % mkdir devtcc; cd devtcc % CC=/matz/git/tinycc/tcc -B/matz/git/tinycc/ ../gcc/configure \ --disable-bootstrap --enable-languages=c,c++,fortran,java,objc % make -j8 Recent checkouts of GCC will also have the va_arg fix already applied, so it should build well out of box with tcc's mob branch. Note that I checked only the above self-build of gcc (i.e. including building its own runtime libs), I didn't run the testsuite; weekend was running out :) Ciao, Michael. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
