Re: (FWD) Re: Progs linked against libstdc++ dead...
John Polstra wrote: David O'Brien wrote: Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? I think that's the best solution for now. Especially since the bug that may be caused by vtable thunks is greatly outweighed by the Bug Of Not Working At All :-) -- Keith Walker, Spokane, WA FreeBSD 4.0-CURRENT (ASUS) #39: Sat May 1 17:47:40 PDT 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
David O'Brien wrote: I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Good. I didn't know whether it was something they were actively working on. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? I think that's the best solution for now. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
On Fri, 30 Apr 1999, David O'Brien wrote: # These are good questions, and I don't know enough yet about the issues # surrounding vtable thunks to answer them. # # I haven't had time to really dig into this yet. Hopefully Saturday. I'm # about to revert the change until I can see what the problem is and what # the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug # time frame. Of course I will try to upgrade us to it (well 1.2.1 which I # figure will quickly follow). The EGCS maintainers are pushing to get # vtable thunks working properly for 1.2. They seem to work now, but I'll reserve the final judgement for the experts. :-) # Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has # posted a bug report related to them, there is an option to turn them off, # and this *is* -CURRENT. I may just leave them turned on by default. # # Opinions? I'd like to see them left on. # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
On Fri, 30 Apr 1999, David O'Brien wrote: These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? I would prefer to keep vtable thunks turned on. The alternative produces wretched code for multiple inheritance. Personally, I want -fnew-abi too; gcc does some disgusting things with multiple zero-sized base classes without it... -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
On Fri, 30 Apr 1999, David O'Brien wrote: These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? *gritting teeth* bring it on! :) -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
(FWD) Re: Progs linked against libstdc++ dead...
- Forwarded message from Steve Price spr...@hiwaay.net - # Remember you asked. :-) # # [ patch elided ... ] # # Thank you sir! I recompiled cc and friends, then the libstdc++, and # Shazam! everything works again. Haven't done an extensive test, but KDE # works and my X10 daemon :-) # # Thank you, thank you, thank you! Note the :-) above, this was said in jest. The patch reverts a change that David made to go back to the old, less efficient C++ vtable support. I have no doubt David will figure out what is wrong and fix it. However, this does bring up a problem that should probably be discussed a little bit more. Since the vtable thunks are more efficient and will eventually be the default, we might ought to stick with them. David mentioned that there might be problems with them, but with enough developers using -current to beat out the kinks we should be able to resolve them in short order. -steve - End forwarded message - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
- Forwarded message from Steve Price spr...@hiwaay.net - Since the vtable thunks are more efficient and will eventually be the default, we might ought to stick with them. David mentioned that there might be problems with them, but with enough developers using -current to beat out the kinks we should be able to resolve them in short order. I doubt it. The problems, according to the egcs team, are compiler bugs. It's unlikely any of us could fix them without going into a trance, smoking the g++ pipe three times a day, and abstaining from sexual relations for a year. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
On Thu, 29 Apr 1999, John Polstra wrote: # - Forwarded message from Steve Price spr...@hiwaay.net - # # Since the vtable thunks are more efficient and will eventually # be the default, we might ought to stick with them. David mentioned # that there might be problems with them, but with enough developers # using -current to beat out the kinks we should be able to resolve # them in short order. # # I doubt it. The problems, according to the egcs team, are compiler # bugs. It's unlikely any of us could fix them without going into a # trance, smoking the g++ pipe three times a day, and abstaining from # sexual relations for a year. Fair enough, but the problem that really concerns me is that all the C++ libraries (and the programs that use them) will have to be recompiled when we make the switch. Is there a programatic way to tell which vtable implementation a library was compiled with? The compile-time error message doesn't count. Turning the new vtable implementation on at any time now or in the future is going to cause confusion. I guess the real question is will turning it on by default now make for less problems than waiting a month or two and then flipping the switch? -steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: (FWD) Re: Progs linked against libstdc++ dead...
In article pine.osf.4.10.9904291305480.2845-100...@fly.hiwaay.net, Steve Price spr...@hiwaay.net wrote: Fair enough, but the problem that really concerns me is that all the C++ libraries (and the programs that use them) will have to be recompiled when we make the switch. Is there a programatic way to tell which vtable implementation a library was compiled with? The compile-time error message doesn't count. Turning the new vtable implementation on at any time now or in the future is going to cause confusion. I guess the real question is will turning it on by default now make for less problems than waiting a month or two and then flipping the switch? These are good questions, and I don't know enough yet about the issues surrounding vtable thunks to answer them. We'll of course try to avoid the need to recompile libraries, but if that turns out to be impossible ... well, this is -current, after all. :-} John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
