Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 21 Aug 2004 01:27:46 +0200 From: "Gerrit P. Haase" Reply-To: "Gerrit @ cygwin" Organization: Esse keine toten Tiere Message-ID: <1035501656.20040821012746@familiehaase.de> To: cygwin AT cygwin DOT com Subject: Re: Updated: gcc-3.3.3-3 In-Reply-To: <20040820141724.GD338@trixie.casa.cgf.cx> References: <200408201340 DOT i7KDeOn23283 AT esds DOT vss DOT fsi DOT com> <20040820141724 DOT GD338 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Christopher writes: > On Fri, Aug 20, 2004 at 02:52:02PM +0100, Dave Korn wrote: >>> -----Original Message----- >>> From: cygwin-owner On Behalf Of Gerrit P. Haase >>> Sent: 20 August 2004 14:40 >> >>> NEWS >>> ==== >>> In this release the option '-fschedule-insns2' was disabled >>> for '-O2' or greater optimization >> >>> The change (against 3.3.3-2 sources) for Cygwin builds looks >>> as follows: >>> --- gcc-3.3.3-3-orig/gcc/toplev.c 2003-12-23 >>> 07:28:29.000000000 +0100 >>> +++ gcc-3.3.3-3/gcc/toplev.c 2004-08-19 14:39:39.911977900 +0200 >>> @@ -4900,8 +4907,12 @@ >>> flag_peephole2 = 1; >>> #ifdef INSN_SCHEDULING >>> flag_schedule_insns = 1; >>> +#ifdef __CYGWIN__ >>> + flag_schedule_insns_after_reload = 0; >>> +#else >>> flag_schedule_insns_after_reload = 1; >>> #endif >>> +#endif >>> flag_regmove = 1; >>> flag_strict_aliasing = 1; >>> flag_delete_null_pointer_checks = 1; >>> >>> # END OF PATCH >> This sort of change is much better made in the specs on the whole. Just >>FYI. > Yes, good point Dave. > Ditto. It is just a temporary fix. I hope that we can drop it with 3.4.x. I would be more interested if it helps to build cygserver. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/