From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28749 invoked by alias); 22 Dec 2009 11:16:59 -0000 Received: (qmail 28674 invoked by uid 48); 22 Dec 2009 11:16:41 -0000 Date: Tue, 22 Dec 2009 11:16:00 -0000 Message-ID: <20091222111641.28673.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug rtl-optimization/38644] Optimization flag -O1 -fschedule-insns2 causes wrong code In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rearnsha at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-12/txt/msg02090.txt.bz2 ------- Comment #5 from rearnsha at gcc dot gnu dot org 2009-12-22 11:16 ------- IMO this is a generic bug in the scheduler. The code in sched-deps.c should note that STACK_POINTER_RTX is being changed and insert a memory barrier that prevents migration of stack-related memory accesses across the change. Of course, determining what memory accesses are stack-related is quite hard, and it may be that all memory accesses in the same address space as the stack will need to be restricted. -- rearnsha at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |rtl-optimization Last reconfirmed|2009-03-17 00:03:45 |2009-12-22 11:16:40 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38644