tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] 0.9.26 regression on WIN32 - utime() links to _utime3


From: Roy Tam
Subject: Re: [Tinycc-devel] 0.9.26 regression on WIN32 - utime() links to _utime32 instead of _utime in msvcrt.dll
Date: Wed, 26 Mar 2014 08:04:54 +0800

2014-03-26 0:10 GMT+08:00 Peter <address@hidden>:
> ----------------------------------------
>> From: address@hidden
>> Date: Tue, 25 Mar 2014 21:19:33 +0800
>> To: address@hidden
>> Subject: Re: [Tinycc-devel] 0.9.26 regression on WIN32 - utime() links to 
>> _utime32 instead of _utime in msvcrt.dll
>>
>> 2014-03-25 20:47 GMT+08:00 Peter <address@hidden>:
> ...
>>> I have discovered the following problem and submitted a bug 
>>> http://savannah.nongnu.org/bugs/index.php?41950
>>>
>>> The following simple program:
>>>
>>> &include <sys/utime.h>
>>>
>>> int main(int argc, char **argv)
>>> {
>>> utime(argv[1], 0);
>>> }
>>>
>>> compiled win 0.9.26 on WIN32 (Windows XP SP3) links to the - non existing - 
>>> _utime32 export from msvcrt.dll instead of the correct one (_utime). It 
>>> compiles correctly with 0.9.25.
>>>
>>> There is a ZIP file with all the relevant files attached to the bug report.
>>>
>>
>> Did you try the tip revision in mob branch?
>> I can't reproduce the bug in mob branch, so it may be fixed in mob branch.
>
> Just now I compiled the tcc mob branch. This was the first time ever I used 
> git so I hope the chekout is correct. I attached the resulting tcc "distro" 
> in the bug at http://savannah.nongnu.org/bugs/index.php?41950 
> (20140325_tcc_mob_ruevs.zip). You can see my build process in BuildLog.txt 
> inside the zip file.
>
> The resulting tcc.exe is different from the 0.9.26 release (normal) but 
> unfortunately the tccutimebug.exe it compiles is identical to the problematic 
> one compiled by the official release (tccutimebug_0926.exe).
>
> Another thing I noticed is that the tcc.exe I built still reports 0.9.26 - is 
> this normal? Is the version number kept at the last release level during 
> development in the mob branch?

Oops, I just forget that I have some local patches that haven't pushed
to mob branch.

> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Attachment: i386-asm.patch
Description: Binary data

Attachment: my-mingw.patch
Description: Binary data

Attachment: utime_mgw64.patch
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]