From: Danny S. <dan...@cl...> - 2003-01-28 20:08:27
|
----- Original Message ----- From: "Earnie Boyd" <ear...@ya...> To: <min...@li...> Sent: Tuesday, 28 January 2003 11:03 Subject: Re: [MinGW-dvlpr] gcc 3.2.1 RC->release > Danny Smith wrote: > > > > Question: Does mingw want to continue to pretend to support i386? If > > so it means that thread support in libstdc++ must use some slow generic > > code rather than inline asm that uses insns that are not available to > > i386 (but are to i486 and higher). FWIW, libstdc++ thread support for > > i386 has been broken in 3.0-3.2 and no one has complained. > > > > I would be happy to move beyond i386. If anyone complains, they can > always build it themselves. Will the specs move to i486 as the default > architecture? > No. The only thing that needs to be changed is to make the default libstdc++ atomicity.h correspond to the i486 version not the generic version. So, the only breakage would occur would be on i386 in app using threads in C++. We could change the default arch to i486 if desired (and break a lot more apps running on i386), but I don't think it will affect performance very much. Danny > Earnie. > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |