Re: [Tinycc-devel] 114_bound_signal error when tcc is compiled by tcc on macOS M1, new -arch behavior
Thank you Grischka. I understand your point and can perfectly leave with it. We'll reconsider this option when: - tcc will be able to generate native arm64 code (probably not too hard, there are only issues with reloc) - when we decide to allow generation of either x86_64/arm64 with two different drivers (like -m32/-64 on Windows) Have a nice day. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of grischka Sent: Thursday, August 05, 2021 17:40 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] 114_bound_signal error when tcc is compiled by tcc on macOS M1, new -arch behavior Christian Jullien wrote: > Hi folks, > Hi Christian, > gcc: error: this compiler does not support arm64 <= Sad > Grischka, can you please reconsider this choice as it seems dangerous to > me to ignore argument? Please note that my error message was the same as > gcc. I did make considerations of course and I think the conclusion was that this is category "fragmentary feature". The error message may be the same as with gcc but all the rest required to make it a feature useful for other people is absent. There was some aspect of "unnecessarily different" too. tcc -hh already has a list the ignored options, there was no need to add an extra line explaining that -arch is ignored now too. It may be arguable how user-friendly or "dangerous" tcc is with how it ignores some options, however I do not see the argument to handle specifically this one differently. Rsp. arguments always exist of course but do they justify the extra effort, that is the consideration to be made. --- grischka > > > > C. > > ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] 114_bound_signal error when tcc is compiled by tcc on macOS M1, new -arch behavior
Christian Jullien wrote: Hi folks, Hi Christian, gcc: error: this compiler does not support arm64 <= Sad Grischka, can you please reconsider this choice as it seems dangerous to me to ignore argument? Please note that my error message was the same as gcc. I did make considerations of course and I think the conclusion was that this is category "fragmentary feature". The error message may be the same as with gcc but all the rest required to make it a feature useful for other people is absent. There was some aspect of "unnecessarily different" too. tcc -hh already has a list the ignored options, there was no need to add an extra line explaining that -arch is ignored now too. It may be arguable how user-friendly or "dangerous" tcc is with how it ignores some options, however I do not see the argument to handle specifically this one differently. Rsp. arguments always exist of course but do they justify the extra effort, that is the consideration to be made. --- grischka C. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
[Tinycc-devel] 112_backtrace invalid memory access found on riscv64
Hi, Just tested on Debian riscv64, ./configure --cc=clang --prefix=/home/jullien/tinycc/static Binary directory/home/jullien/tinycc/static/bin TinyCC directory/home/jullien/tinycc/static/lib/tcc Library directory /home/jullien/tinycc/static/lib Include directory /home/jullien/tinycc/static/include Manual directory/home/jullien/tinycc/static/share/man Info directory /home/jullien/tinycc/static/share/info Doc directory /home/jullien/tinycc/static/share/doc Source path /home/jullien/tinycc C compiler clang (11.0) Target OS Linux CPU riscv64 Triplet riscv64-linux-gnu I've got Test: 112_backtrace... --- 112_backtrace.expect2021-08-05 06:43:52.475956663 + +++ 112_backtrace.output2021-08-05 06:54:24.806748723 + @@ -3,11 +3,7 @@ * f1() * f2() * f3() -112_backtrace.c:9: at f3: RUNTIME ERROR: invalid memory access -112_backtrace.c:14: by f2 -112_backtrace.c:19: by f1 -112_backtrace.c:24: by main -[returns 255] +* exit main [test_bcheck_1] * main gmake[3]: *** [Makefile:133: 112_backtrace.test] Error 1 ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
