Modifying Win32 default optimizations?

2005-05-11 Thread William A. Rowe, Jr.
I'd like to modify the Win32 build projects (of mod_jk, and httpd 1.3/2.0/2.1-dev, along with apr); The /O2 optimization option is extremely agressive, unfortunately it produces less than ideal crash traceback information. That is due to the (implicit) /Oy flag, which omits respecible stack

Re: Modifying Win32 default optimizations?

2005-05-11 Thread William A. Rowe, Jr.
At 08:46 AM 5/11/2005, Branko Čibej wrote: All in all - comments? How about moving away from MSVC 6 to (say) VC.Net 2003, while we're at it? It's time, to say the least. Not for 1.3 or 2.0 httpd - you lose some measure of binary compatibility. We can jump through hoops to continue to use the

Re: Modifying Win32 default optimizations?

2005-05-11 Thread William A. Rowe, Jr.
At 04:35 PM 5/11/2005, Branko Čibej wrote: William A. Rowe, Jr. wrote: If the open source community tends to push back on Microsoft's newest compilers, it's simply because their forced treadmill is the anathema of inclusiveness. That's what's happening right now with Subversion. The Python 2.4

Re: Modifying Win32 default optimizations?

2005-05-11 Thread William A. Rowe, Jr.
At 08:29 PM 5/11/2005, Randy Kobes wrote: That sounds great, but one consideration from the point of view of Perl (eg, mod_perl) is that the dominant Win32 Perl binary, from ActiveState, uses VC 6 to compile, and they don't have any plans soon of changing that. But that might change by the next