Ok I fixed it taking care of gcc version.
http://repo.or.cz/tinycc.git/commitdiff/ed99f3608df3d6dd4c8c7d52d608a8212203
dfe4
Looks good now on Fedora 25.
C.
-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of grischka
Sent: mardi 2
From: Tinycc-devel [mailto:tinycc-devel-bounces+nuke48386=yahoo@nongnu.org]
On Behalf Of Hernán J. González
Sent: Tuesday, November 29, 2016 2:53 PM
To: tinycc-devel@nongnu.org
Subject: [Tinycc-devel] sleep() interprets argument as milliseconds instead of
seconds
The POSIX sleep()
The POSIX sleep() function ( ) should interpret is input
argument as seconds.
TinyC seems to interpret it as milliseconds.
Using tcc version 0.9.26
/***/
#include
#include
int main() {
int i;
fputs("Looping ...\n",stdout);
for(i=0;i<10;i++) {
fputs(".",stdo
Indeed, I missed this information. Thank you for your help.
Well, I found some documentation where the tcc_set_output_type() function
was called after compilation, and it work fine like that, so I didn't
wonder that TCC was not able to do both outputs with a single compilation.
The question about w
Christian Jullien wrote:
GCC documentation says:
Calling this function with a nonzero argument can have unpredictable
effects, including crashing the calling program. As a result, calls that are
considered unsafe are diagnosed when the -Wframe-address option is in
effect. Such calls should onl
