Kai Tietz schrieb:
> 2009/8/31 Wolfgang Glas <[email protected]>:
>> Hi all,
>>
>> We appreciate very much the efforts to bring forward the latest and greatest
>> gcc technology to Windows by publishing gcc-4.5 based snapshots ;-)
>>
>> However, since our company is developping Windows software we need to rely
>> on
>> a stable compiler and hence are quite happy with the gcc-4.4 release series
>> for
>> the moment.
>>
>> I've noticed that gcc-4.4.1 has been released quite a while ago, so my
>> question is whether there are plans to release a mingw-w64-4.4.1 tarball in
>> succession to the mingw-w64-4.4.0 tarball. We are really satisfied with the
>> 4.4.0 release and would like to have the upstream bufixes integrated in the
>> stable compiler series at some point in time.
>>
>> If there are no plans and/or no resources to prepare such a tarball, I may
>> as
>> well contribute one. However, I may need some advice on which components I
>> should update.
>>
>> Best regards,
>>
>> Wolfgang
>
> Hello Wolfgang,
>
> the next version for 4.4 branch, we will release, is 4.4.2 as it has
> some major fixes for x64 code. So if you want to use newer version of
> gcc, I would recomment not using 4.4.1, and instead 4.4.2 (at the
> moment as pre-release available).
> Also we plan to do our first stable release of runtime soon. We are
> working at the moment hard to finalize some things, like header,
> library, and top-level configure, and also to fix remaining issues
> found in our header-set. We plan to do this end of September beginning
> October this year.
Hello Kai,
That's very good news, ThX very much ;-) I'm currently debianizing
mingw-w64-4.4.0-1, which works very good for our projects.
The following questions arose at this point:
1) Have you already applied the attached patch, which fixes the reference to the
symbol _ftime32(), which is really called _ftime() in msvcrt.dll ?
2) Can you recommend a stable binutils release or should I stick to the snapshot
included in mingw-w64-4.4.0-1 ?
3) Will your gcc-4.4.2 package use dwarf-2 exception handling like the packages
from www.mingw.org ?
4) Are there gcc-4.4-based snapshots available ?
Best regards and TIA,
Wolfgang
--- sys/timeb.h.orig 2009-03-27 11:13:44.000000000 +0100
+++ sys/timeb.h 2009-05-21 13:03:16.000000000 +0200
@@ -83,14 +83,13 @@
#ifdef _USE_32BIT_TIME_T
#define _timeb __timeb32
-#define _ftime _ftime32
+ _CRTIMP void __cdecl _ftime(struct __timeb32 *_Time);
#else
#define _timeb __timeb64
#define _ftime _ftime64
#endif
#endif
- _CRTIMP void __cdecl _ftime32(struct __timeb32 *_Time);
#if _INTEGRAL_MAX_BITS >= 64
_CRTIMP void __cdecl _ftime64(struct __timeb64 *_Time);
#endif
@@ -111,7 +110,7 @@
#if !defined (RC_INVOKED) && !defined (NO_OLDNAMES)
#ifdef _USE_32BIT_TIME_T
__CRT_INLINE void __cdecl ftime(struct timeb *_Tmb) {
- _ftime32((struct __timeb32 *)_Tmb);
+ _ftime((struct __timeb32 *)_Tmb);
}
#else
__CRT_INLINE void __cdecl ftime(struct timeb *_Tmb) {
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
