Hi,
On Sun, 31 Dec 2017, foobar wrote:
please find attached code that exposes a codegen bug in tcc, resulting
in an endless loop in libtom's embedded bigmath code on x86_64 musl
linux.
(note: the code in main() under #if 0 exposes another problem, no
endless loop, but wrong result)
it see
On Sat, 30 Dec 2017 21:48:24 +
foobar wrote:
> please find attached code that exposes a codegen bug in tcc, resulting in an
> endless loop in libtom's embedded bigmath code on x86_64 musl linux.
>
> (note: the code in main() under #if 0 exposes another problem, no endless
> loop, but wrong
Hi,
On Thu, 28 Dec 2017, grischka wrote:
Ok, I was able to reproduce the original problem on an suse 10.2 from
2007.
He :)
It is that in debug mode, tcc includes all sections in the image,
that is also reloc sections that already have been applied.
Hah, finally a reason to fix this long s
Hi,
On Thu, 28 Dec 2017, foobar wrote:
$ cat test.c
int t(int x) { return f(x)+1; }
$ tcc test.c -c -Werror || echo error
test.c:1: warning: implicit declaration of function 'f'
error
$ tcc test.c -c -Werror-implicit-function-declaration || echo error
test.c:1: warning: implicit declaration o
Hi,
On Tue, 26 Dec 2017, Michael B. Smith wrote:
No. Warnings are never required diagnostics (and even if, what
specifically would you want to warn about in this case?). The only
require diagnostics are from constraint violations. Most other
undefined behaviours don't need to be diagnosed
