> I'd prefer a patch that just gives a warning for unknown -W option. And how about the test case: tcc -Wunsupported -traditional -E tcc.c -o tcc.i What is purpose of the -Wunsupported ? How to tell a tcc don't break a compilation process if there is an unknown option? Consider a compilation of the linux kernel.
2015-01-05 0:01 GMT+03:00, RoboTux <[email protected]>: > Le 2015-01-04 04:42, Sergey Korshunoff a écrit : >>> GCC and clang also error out for unknown option. What option caused >>> your >> program to fail to compile? >> >> The patch is for the case with -Wunsupported. In such case a user will >> is "Don't trap, only warning". There are many gcc options which tcc >> don't support. But in many cases, this options are not important. >> Changing a Makefiles is not a solution when trying to use tcc insteed >> of gcc. >> And a patch test command is: >> /tcc -Wunsupported -traditional -E tcc.c -o tcc.i > > I'd prefer a patch that just gives a warning for unknown -W option. It > would be just like if the detection was really bad. Doing the same for > other options would be more risky IMHO. That would avoid rewriting the > Makefile to only add switches to CFLAGS that are supported by the > compiler as it should have been done ;-) (no blame, we all do this). > > Best regards, > > Thomas > _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
