Re: gcc 3.1 / streambuf.h broken with using namespace std;
On Saturday, August 31, 2002, at 06:04 PM, Terry Lambert wrote: David O'Brien wrote: Because rather than leaving it alone for a while, they are already planning a 3.3. 8-). And comments on this list to that effect. I don't follow. The GCC group branches previous to a release and makes an initial + point releases from it. I thought it was the general consensus that the 3.1 version of the compiler was broken, and generated bad code, and that the 3.2 compiler had a lot of these problems corrected, but destroyed binary compatability with 3.1. Yes but if you go through and read gcc.gnu.org you will see that 3.2 can be configured on linux to use the multi-vendor ABI standard. Actually they have been trying to make this work all along and is probably why they break ABI compatibility. 3.1 has issues with template classes that use functions containing static variables [at least a pre-release of it did on Darwin/OS X]. This kind of bug made 3.2 necessary for some people [though I hope every time the fix something that their test-cases increases by one that would be smart anyway]. 3.2 is the more confident ABI and while there are no guarantees that 3.3 will work with 3.2... there seems to be better feelings about it. I guess the fear is that, if they are willing to destroy binary compatability between point releases, with another point release in the wings, it would be risky to pick the point release one behind to standardise upon. There will hopefully always be one behind its called progress. They haven't implemented export yet so they don't have a 100% compliant C++ compiler yet either... no reason to stop. It was my understanding that FreeBSD 5.0 release was not going to be GCC 3.3 (because GCC 3.3 would not be released in time for FreeBSD to not be pulling a RedHat if they shipped a beta and called it 3.3) , might be GCC 3.2, and was currently down-rev from there. RedHat actually created a release that never occurred [2.96] in the gcc release chain... and if you use it, its actually a pretty nice compiler I know the ABI doesn't work with anything but 2.96 though. How is this different from FreeBSD? (other than they branch much before the .0 release and we don't). FreeBSD has been been branched for 18 months before the 5.0 release; what are you talking about?!? There's not much more much than that, in the entire history of GCC. I thought the comparison was pretty clear myself... FreeBSD current is branched from the same CVS then worked on... the STABLE folks don't usually start whining about all the stuff that's going to be broken for them maybe not until DP2 anyway. :) -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gcc 3.1 / streambuf.h broken with using namespace std;
It is *that* simple. yep. Rather than bitch that 3.1.1 sucks; we should thanking the GCC Steering Committee that after much thought they were willing to take the vendors' needs into account. I am not sure FreeBSD would have done the same. I never said it sucked... I think the ABI standardization process is *very* important as it will be an enabling technology... these things don't come without some growing pains. Actually they have been trying to make this work all along and is probably why they break ABI compatibility. 3.1 has issues with template classes that use functions containing static variables [at least a pre-release of it did on Darwin/OS X]. Apple highly modifies the GCC sources. So any bugs/problems/issues you find in their compiler you cannot blame on the GCC developers w/o researching the bug/problem/issue. Wasn't aware to what degree GCC is modified by Apple... I knew they did some things... 3.2 necessary for some people [though I hope every time the fix something that their test-cases increases by one that would be smart anyway]. The test suite does. We should be so lucky to have such a test suite. Indeed! :) 3.2 is the more confident ABI and while there are no guarantees that 3.3 will work with 3.2... there seems to be better feelings about it. Correct. Not only better feelings but fully intended. But as we saw with 3.1.0, bugs happen. Yes... I think you and I are generally on the same page :). It was my understanding that FreeBSD 5.0 release was not going to be GCC 3.3 (because GCC 3.3 would not be released in time for FreeBSD to not be pulling a RedHat if they shipped a beta and called it 3.3) , might be GCC 3.2, and was currently down-rev from there. 3.3.0 will be released before FreeBSD 5.1. It is my advice to FreeBSD'ville that we go with a GCC 3.3 snapshot for FBSD 5.0 and a GCC 3.3.0 release for FBSD 5.1. That way we can get the new features of 3.3 into our 5.x branch. AND get bug fixes by importing 3.3.1 and 3.3.2 into later FBSD 5.x releases. Yes! yes! YES! :) 100% agree! IMO DP-2 should have gcc-3.3 snap perhaps even FreeBSD 5.0 release [assuming that 5.0 is released on November 20, 2002... I have doubts but I'd rather it be done properly than done quickly... Its one reason I like FreeBSD and the community.] Seems like things are going exactly as they should... going to 3.3 should greatly decrease developer pain overall. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
new.
Hey... I am new here and just want to check things out for a bit and see if I can't pitch in... At the very least I will try to build CURRENT from time to time and run some programs... maybe somewhere down the road I can commit something worthwhile. I also wanted to see if my filter worked on my email :) Looking forward to working with you all... Dave Leimbach To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: new.
Darwin is just one of my pursuits :) I am currently just going to play around with current when I have time :) I actually do care to make FBSD 5.0 kickass if I can help... even as a tester. Dave On Monday, August 19, 2002, at 09:13 PM, Alex Zepeda wrote: On Mon, Aug 19, 2002 at 08:19:53PM -0500, [EMAIL PROTECTED] wrote: Looking forward to working with you all... What? Darwin wasn't good enough for you? Yuk, yuk, yuk. Good luck getting it running :) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: new.
Thanks for the tip! On Monday, August 19, 2002, at 09:21 PM, Mike Barcroft wrote: [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Hey... I am new here and just want to check things out for a bit and see if I can't pitch in... At the very least I will try to build CURRENT from time to time and run some programs... maybe somewhere down the road I can commit something worthwhile. I also wanted to see if my filter worked on my email :) Looking forward to working with you all... You might want to get started by reading Michael Lucas' article on testing -current: http://www.onlamp.com/pub/a/bsd/2002/04/18/Big_Scary_Daemons.html Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
