I just recompiled you test program with mob. On Windows, cl, clang, gcc and ...
tcc all produce the same output result.
Sorry, I can't reproduce.
C.
-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On
Behalf Of Vincent Lefevre
Sent: Sunday,
Since I had not enough permissions to install TCC
Le 13/12/2020 à 21:35, Anton Shepelev a écrit :
> Since I had not
> enough permissions to install TCC
--
-- sibian0...@gmail.com
-- Développeur compulsif
___
Tinycc-devel mailing list
Tinycc-devel@nongnu
Vincent Lefevre:
> No issue with tcc 0.9.27+git20200814.62c30a4a-1 provided
> by Debian.
The bug on my side is reproduced with this version just five
days old:
https://repo.or.cz/tinycc.git/snapshot/8ff705554de47f16726ec5f1a6c49a162b926732.zip
I had to compile it myself on Windows, using
wi
On 2020-12-13 14:40:17 +0300, Anton Shepelev wrote:
> Hello, all
>
> During the recent exercise in comp.lang.c in writing a C
> program to strip comments from a C source, I have
> encountered what seems to be a bug in TCC. It is manifest
> when compiling looser drug's entry with TCC and feeding i
Hello, all
During the recent exercise in comp.lang.c in writing a C
program to strip comments from a C source, I have
encountered what seems to be a bug in TCC. It is manifest
when compiling looser drug's entry with TCC and feeding it
the following test input (between --- markers):
---
a/\
\
\
\
