From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4869 invoked by alias); 15 Jan 2002 21:06:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 4855 invoked by uid 71); 15 Jan 2002 21:06:00 -0000 Date: Tue, 15 Jan 2002 13:06:00 -0000 Message-ID: <20020115210600.4854.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Ted Merrill Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm Reply-To: Ted Merrill X-SW-Source: 2002-01/txt/msg00571.txt.bz2 List-Id: The following reply was made to PR target/4508; it has been noted by GNATS. From: Ted Merrill To: Richard.Earnshaw@arm.com Cc: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, rearnsha@arm.com Subject: Re: target/4508: [ARM] gcc 3.0, ARM/thumb target, generates invalid asm Date: Tue, 15 Jan 2002 12:56:52 -0800 (PST) I am now unable to replicate the original problem using the files that i saved and what i believe is the original compiler. (It did happen, i'm not really crazy). Send this to the Journal for Unreproducible Phenomenom i guess. Close the issue... Thanks, Ted Merrill On Tue, 15 Jan 2002, Richard Earnshaw wrote: > > Ted, > > I'm sorry I've not been more pro-active on this, I've been overloaded with > other issues recently, plus I was on sabatical late last year. > > It is a bit difficult even for me here to accept code that might be > considered confidential (our lawyers would probably have something to say > about it unless there was some form of legal agreement in place). > However, I don't think there is any need, since I suspect that I already > know what the basic problem is here. > > If the problem is what I think, then I believe the latest CVS copy of the > compiler has a fix for this bug installed now. I would be grateful if you > could find a chance to check it out and try it on your problem code, > please let us know how you get on, then we can close this report. > > R. > >