From: <dan...@ya...> - 2001-01-16 21:26:43
|
--- Mumit Khan <khan@NanoTech.Wisc.EDU> wrote: > Is there anyone working on this issue? I just looked at Earnie's > patch > (thanks!), and it looks ok. I'd like to run the dejagnu testsuite on > it first of course. > > Is there a preferred binutils these days? I know that Paul Sokolovsky > has > a test version. Without having to go through the sources, does anyone > know > off-hand how it differs from DJ's latest binutils for Cygwin? > > Regards, > Mumit I have built and tested the prerelease (with stlport, fltk, libodbc++, and their regression testsuite, but notwith dejagnu testsuite) and no new problems. Re: native-struct I also tried to make bootstrap with CFLAGS=-DDEFAULT_NATIVE_STRUCT. This failed at stage1 compiler (genattrtab.exe produces broken insn-attrtab.c) But this was successful: CFLAGS=-DDEFAULT_NATIVE_STRUCT -fgcc-struct and produces native packed structures. Also have built with -DDEFAULT_VTABLE_THUNKS=2 and no problems yet. I haven't tested the gcc-2.95.2 with Pauls binutils, but have used same source as latest Cygwin binutils, but with libbfd built as dll. If we go with -fnative-struct as default, I think we could run into dll problems (eg binutils linking against old versions of libbdfd.dll, built with gcc-struct, in path). Need to be careful here. Regards Danny _____________________________________________________________________________ http://au.classifieds.yahoo.com/au/car/ - Yahoo! Cars - Buy, sell or finance a car.. |
From: <dan...@ya...> - 2001-01-16 22:19:59
|
--- Mumit Khan <khan@NanoTech.Wisc.EDU> wrote: > On Wed, 17 Jan 2001, > > Excellent, thank you. However, one big challenge is first to test the > compiler itself, since most of the corner cases are usually not > caught > by various packages. What patchsets are you using on top of the > official > sources? Just Earnie's? I'd like to build the same set here, and want > to avoid deviations. > Actually, I applied your mingw-gcc-2.95.2-1 diff file from Jan 2000 (after breaking it up by directory) Also, changed configure script to make msvcrt.dll default and added Thomas Pfaff's __gthread_getspecific patch for GetLastError to gthread_win32.h > > Re: native-struct > > I also tried to make bootstrap with CFLAGS=-DDEFAULT_NATIVE_STRUCT. > > > This failed at stage1 compiler (genattrtab.exe produces broken > > insn-attrtab.c) But this was successful: > > CFLAGS=-DDEFAULT_NATIVE_STRUCT -fgcc-struct and produces native > packed > > structures. > > Ah, I do remember the problem with stage1 failing with default is the > native struct, but never did get to the bottom of it. I'll take > another > look. I need to remind myself of the issues involved, and I don't > even > remember what -fgcc-struct is supposed to be doing. -fgcc-struct == "-fno-native-struct" (current default) > > Also have built with -DDEFAULT_VTABLE_THUNKS=2 and no problems > yet. > > Note that this causes binary incompatibility since it changes the > ABI. Yes. All my C++ code recently has been built that way. Also I don't use libstdc++ very much anyway, preferring STLPort SGI iostream lib (built with -fvtable-thunks) for iostreams. That may change with g++-v3. Danny _____________________________________________________________________________ http://au.classifieds.yahoo.com/au/car/ - Yahoo! Cars - Buy, sell or finance a car.. |
From: Mumit K. <khan@NanoTech.Wisc.EDU> - 2001-01-16 22:49:50
|
On Wed, 17 Jan 2001, Danny Smith wrote: > Actually, I applied your mingw-gcc-2.95.2-1 diff file from Jan 2000 > (after breaking it up by directory) Also, changed configure script to > make msvcrt.dll default and added Thomas Pfaff's __gthread_getspecific > patch for GetLastError to gthread_win32.h I have all the patches also in "individual" patch format, broken up by functionality, and that really helps ease the process of getting these patches to a newer release. Ok, now we're on the same page as far as patches are concerned. > -fgcc-struct == "-fno-native-struct" (current default) You can tell that I've out of this business for a while. Thanks. > Yes. All my C++ code recently has been built that way. Also I don't > use libstdc++ very much anyway, preferring STLPort SGI iostream lib > (built with -fvtable-thunks) for iostreams. That may change with > g++-v3. We have to maintain binary compatibility among minor releases; it does get broken, and for the better, in v3. It's actually not even relevant that you use STLport -- it'll cause trouble any user code that uses any virtual tables, which is pretty much all C++ code. I'll have to go through the arduous process of setting up dejagnu setup for Mingw testing (long story -- needs all sorts of hacks, and have to use the native expect port due to problems with the Cygwin one), and hopefully can get some testing done. Regards, Mumit |
From: Earnie B. <ear...@ya...> - 2001-01-17 02:50:24
|
Mumit Khan wrote: > > I'll have to go through the arduous process of setting up dejagnu setup > for Mingw testing (long story -- needs all sorts of hacks, and have to > use the native expect port due to problems with the Cygwin one), and > hopefully can get some testing done. > Does Expect expect TK? :) Or does it just use Tcl? If it's just Tcl the UNIX code builds with Cygwin and `gcc -mno-win32'. Cheers, Earnie _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Mumit K. <khan@NanoTech.Wisc.EDU> - 2001-01-17 05:12:36
|
On Tue, 16 Jan 2001, Earnie Boyd wrote: > Does Expect expect TK? :) Or does it just use Tcl? If it's just Tcl the > UNIX code builds with Cygwin and `gcc -mno-win32'. It's a Tcl extension, and the problem is twofold: (1) the native port is very difficult due to things that Expects expects, such as ptys and such; (2) the Cygwin expect suffers from the fact that the Tcl port has lots of trouble with understanding/translating Cygwin filenames, and you have to play some games. On top of that, until recently, Cygwin expect will die after a few thousand tests, but that seems to be gone with Cygwin 1.1.x on W2k. I'm going to try both tomorrow and see how far I get. One or the other will work. I still have the minor mods dejagnu, mostly to handle pathname issues, on a backup CD. Regards, Mumit |
From: Paul G. <pga...@te...> - 2001-01-17 01:01:19
|
Hi folks, On 16 Jan 2001, at 13:19, the Illustrious Mumit Khan wrote: > Is there anyone working on this issue? I just looked at Earnie's > patch (thanks!), and it looks ok. I'd like to run the dejagnu > testsuite on it first of course. > > Is there a preferred binutils these days? I know that Paul > Sokolovsky has a test version. Without having to go through the > sources, does anyone know off-hand how it differs from DJ's > latest binutils for Cygwin? Afaik, it differs only in the fact that it doesn't link the cygwin.dll and it is built using mingw. I suppose Paul S. would need to reply to get a more accurate answer, since mingw binutils are more or less his baby... Peace, Paul G. > > Regards, > Mumit > > > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |
From: <dan...@ya...> - 2001-01-17 01:36:39
|
--- Mumit Khan <khan@NanoTech.Wisc.EDU> wrote: > > We have to maintain binary compatibility among minor releases; it > does > get broken, and for the better, in v3. It's actually not even > relevant > that you use STLport -- it'll cause trouble any user code that uses > any > virtual tables, which is pretty much all C++ code. > Sorry, I wasn't actually proposing to release with default vtable thunks. Just commenting that it seems to be working okay. Danny _____________________________________________________________________________ http://au.classifieds.yahoo.com/au/car/ - Yahoo! Cars - Buy, sell or finance a car.. |
From: Mumit K. <khan@NanoTech.Wisc.EDU> - 2001-01-17 05:22:04
|
On Wed, 17 Jan 2001, Danny Smith wrote: > Sorry, I wasn't actually proposing to release with default vtable > thunks. Just commenting that it seems to be working okay. Oh, I know. Thought I'd point it out mostly for the benefit all those listening in. btw, with vtable-thunks, multiple inheritance has a few interesting problems (shows up on x86-linux-gnu for example), and multiple inheritance in COM doesn't work (I don't know what the correct terminology is for COM, sorry. Multiple dispatch?). If you have ideas, love to hear it. Regards, Mumit |
From: <dan...@ya...> - 2001-01-18 04:40:09
|
--------------------------------------- On Wed, 17 Jan 2001, Danny Smith wrote: > Sorry, I wasn't actually proposing to release with default vtable > thunks. Just commenting that it seems to be working okay. Oh, I know. Thought I'd point it out mostly for the benefit all those listening in. btw, with vtable-thunks, multiple inheritance has a few interesting problems (shows up on x86-linux-gnu for example), and multiple inheritance in COM doesn't work (I don't know what the correct terminology is for COM, sorry. Multiple dispatch?). If you have ideas, love to hear it. Regards, Mumit Is this the C++ virtual inheritance bug with vtable thunks you were referring to: http://gcc.gnu.org/ml/gcc-bugs/2000-06/msg00578.html If so, they are fixed with 2.95.3. The same fix also corrects problem with virtual functions in ctors. http://gcc.gnu.org/ml/gcc-bugs/2000-02/msg00881.html I can't speak for COM and multiple dispatch. COM is evil. > > Is there sufficient interest in a gcc-2.95.3 release? > > Yes, for above reason, if nothing else. Danny _____________________________________________________________________________ http://au.classifieds.yahoo.com/au/car/ - Yahoo! Cars - Buy, sell or finance a car.. |
From: Paul G. <pga...@te...> - 2001-01-18 23:30:11
|
On 18 Jan 2001, at 17:40, the Illustrious Danny Smith wrote: > --------------------------------------- > On Wed, 17 Jan 2001, Danny Smith wrote: > > > Sorry, I wasn't actually proposing to release with default > > vtable thunks. Just commenting that it seems to be working > > okay. > > Oh, I know. Thought I'd point it out mostly for the benefit all > those listening in. > > btw, with vtable-thunks, multiple inheritance has a few > interesting problems (shows up on x86-linux-gnu for example), and > multiple inheritance in COM doesn't work (I don't know what the > correct terminology is for COM, sorry. Multiple dispatch?). If > you have ideas, love to hear it. > > Regards, > Mumit > > > Is this the C++ virtual inheritance bug with vtable thunks you > were referring to: > > http://gcc.gnu.org/ml/gcc-bugs/2000-06/msg00578.html > > If so, they are fixed with 2.95.3. > > > The same fix also corrects problem with virtual functions in > ctors. http://gcc.gnu.org/ml/gcc-bugs/2000-02/msg00881.html > > I can't speak for COM and multiple dispatch. COM is evil. *grin* It is indeed! quid pro quo, so is DirectX ;-) <evil grin...maniacal laughter floods the room> COM= MS Common Object Module DCOM=MS Dynamic Common Object Module Basics: a method to use an object across multiple modules/applications within the same collection of source code... When is COM or DCOM really needed? Peace, Paul G. > > > > Is there sufficient interest in a gcc-2.95.3 release? > > > > > Yes, for above reason, if nothing else. > > Danny > > _________________________________________________________________ > ____________ http://au.classifieds.yahoo.com/au/car/ - Yahoo! > Cars - Buy, sell or finance a car.. > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |
From: Mumit K. <khan@NanoTech.Wisc.EDU> - 2001-01-16 21:39:43
|
On Wed, 17 Jan 2001, Danny Smith wrote: > I have built and tested the prerelease (with stlport, fltk, libodbc++, > and their regression testsuite, but notwith dejagnu testsuite) and no > new problems. Excellent, thank you. However, one big challenge is first to test the compiler itself, since most of the corner cases are usually not caught by various packages. What patchsets are you using on top of the official sources? Just Earnie's? I'd like to build the same set here, and want to avoid deviations. > Re: native-struct > I also tried to make bootstrap with CFLAGS=-DDEFAULT_NATIVE_STRUCT. > This failed at stage1 compiler (genattrtab.exe produces broken > insn-attrtab.c) But this was successful: > CFLAGS=-DDEFAULT_NATIVE_STRUCT -fgcc-struct and produces native packed > structures. Ah, I do remember the problem with stage1 failing with default is the native struct, but never did get to the bottom of it. I'll take another look. I need to remind myself of the issues involved, and I don't even remember what -fgcc-struct is supposed to be doing. > Also have built with -DDEFAULT_VTABLE_THUNKS=2 and no problems yet. Note that this causes binary incompatibility since it changes the ABI. > I haven't tested the gcc-2.95.2 with Pauls binutils, but have used same > source as latest Cygwin binutils, but with libbfd built as dll. If we > go with -fnative-struct as default, I think we could run into dll > problems (eg binutils linking against old versions of libbdfd.dll, > built with gcc-struct, in path). Need to be careful here. Thanks for all the work and the detailed info, it really helps everyone involved. Regards, Mumit |
From: Paul G. <pga...@te...> - 2001-01-17 01:05:04
|
Hi folks, On 16 Jan 2001, at 15:39, the Illustrious Mumit Khan wrote: > On Wed, 17 Jan 2001, Danny Smith wrote: > > > I have built and tested the prerelease (with stlport, fltk, > > libodbc++, and their regression testsuite, but notwith dejagnu > > testsuite) and no new problems. > > Excellent, thank you. However, one big challenge is first to test > the compiler itself, since most of the corner cases are usually > not caught by various packages. What patchsets are you using on > top of the official sources? Just Earnie's? I'd like to build the > same set here, and want to avoid deviations. > > > Re: native-struct > > I also tried to make bootstrap with > > CFLAGS=-DDEFAULT_NATIVE_STRUCT. This failed at stage1 compiler > > (genattrtab.exe produces broken insn-attrtab.c) But this was > > successful: CFLAGS=-DDEFAULT_NATIVE_STRUCT -fgcc-struct and > > produces native packed structures. > > Ah, I do remember the problem with stage1 failing with default is > the native struct, but never did get to the bottom of it. I'll > take another look. I need to remind myself of the issues > involved, and I don't even remember what -fgcc-struct is supposed > to be doing. > > > Also have built with -DDEFAULT_VTABLE_THUNKS=2 and no problems > > yet. > > Note that this causes binary incompatibility since it changes the > ABI. Well, if I recall correctly, there was some discussion about changing the ABI a month or two ago...I could be way off, it seems it had to do with something about integrating both crtdll and msvcrt under Cygwin...still can't recall all the details... Don't even know if this helps...but thought I'd chime in just the same.. Peace, Paul G. > > > I haven't tested the gcc-2.95.2 with Pauls binutils, but have > > used same source as latest Cygwin binutils, but with libbfd > > built as dll. If we go with -fnative-struct as default, I > > think we could run into dll problems (eg binutils linking > > against old versions of libbdfd.dll, built with gcc-struct, in > > path). Need to be careful here. > > Thanks for all the work and the detailed info, it really helps > everyone involved. > > Regards, > Mumit > > > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |
From: Earnie B. <ear...@ya...> - 2001-01-17 02:27:53
|
Paul Garceau wrote: > > Well, if I recall correctly, there was some discussion about > changing the ABI a month or two ago...I could be way off, it > seems it had to do with something about integrating both crtdll > and msvcrt under Cygwin...still can't recall all the details... Uhm... you're way off. Actually this isn't recallable to anything I can remember. Cygwin's next gcc release will support MSVCRT instead of CRTDLL. > > Don't even know if this helps...but thought I'd chime in just > the same.. Thanks for chiming in. Cheers, Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |