From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26040 invoked by alias); 18 Feb 2004 09:13:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26008 invoked by alias); 18 Feb 2004 09:13:06 -0000 Date: Wed, 18 Feb 2004 09:13:00 -0000 Message-ID: <20040218091306.26007.qmail@sources.redhat.com> From: "wilson at specifixinc dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20020909143600.7871.rz@linux-m68k.org> References: <20020909143600.7871.rz@linux-m68k.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug optimization/7871] [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems X-Bugzilla-Reason: CC X-SW-Source: 2004-02/txt/msg01778.txt.bz2 List-Id: ------- Additional Comments From wilson at specifixinc dot com 2004-02-18 09:13 ------- Subject: Re: [3.3/3.4/3.5 regression] ICE on legal code, global register variables problems On Wed, 2004-02-18 at 01:06, giovannibajo at libero dot it wrote: > Just for the sake of completeness, on which platform did you see this > behaviour? FWIW, Ulrich reported that it fixes the s390 regression on 3.3. This is using the testcase Richard Henderson posted in comment #4, which is for the m68k. The problem is target independent, but it requires a specific set of events which may be uncommon: set a global reg, call a function, set the global reg again using the previous value (set by the call). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7871