Re: [MinGW-dvlpr] Re: gcc 3.1 [-mno-cygwin and __main ]

[<dan...@ya...>]

> 
> Perhaps it's time to drop the -mno-cygwin support and just supply a cygwin
> hosted
> mingw32 targeted cross compiler?
> 
> Earnie.
> 

That is a key question.

I've modified the last patchset i've submitted to fix some crtend.o problems
and tested with;

#!/bin/sh.exe
../gcc/configure  --with-gcc --with-gnu-ld --with-gnu-as --host=mingw32
--target=mingw32 --prefix=/mingw  --enable-threads --disable-nls
--enable-languages=c,c++ --disable-win32-registry --disable-shared
make  bootstrap
make install
make check

and with

#!/bin/sh.exe
../gcc/configure  --with-gcc --with-gnu-ld --with-gnu-as   --enable-threads
--disable-nls --enable-languages=c,c++ --disable-win32-registry
--disable-shared --host=i686-pc-cygwin --target=i686-pc-cygwin
make  bootstrap
make install
make check

and Dwarf2 exception handling works for mingw and cygwin. The testsuite for
cygwin -mno-cygwin will run tonight (sorry I have a slow machine: the testsuite
is a "midnight queue" job for me.)

The cygwin and mingw tests were done with "release" versions of respective
runtimes. No mods,  so backward compat seems okay. 

However, if we remove the constaints of 
(1) maintain backward compat with old (1.3 and earlier) mingw runtime.
(2) maintain compat with cygwin -mno-cygwin 

then the whole move to Dwarf2 EH can be much simpler and may be easier to
maintain for, say GCC 3.2, if gcc/libgcc2.c changes.

Why am I hung up on Dwarf2 EH?

(1) It is more efficient (smaller and faster apps).
(2) sjlj exception handling does not receive much attention in GCC development.
It is becoming a poor relative and will be left behind by mainstream develop.


Back to the question.  How important is maintaining cygwin -mno-cygwin compat
if it restricts or adds cost to mingw progress?  

We owe great debt to cygwin as offspring and (for me, at least) use of the
development tools provided by cygwin and testing in broader environ. IMO,
keeping mingw and cygwin in developmental sync is a good thing.  But at a small
cost. How do other mingw developers percieve the cost?


Danny  
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> MinGW-dvlpr mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr 

http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Save your important files online for easy access!