From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 584 invoked by alias); 29 Dec 2009 21:44:31 -0000 Received: (qmail 527 invoked by alias); 29 Dec 2009 21:44:20 -0000 Date: Tue, 29 Dec 2009 21:44:00 -0000 Message-ID: <20091229214420.526.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/40414] gcc 4.4.0 error at postreload.c:396 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "joseph at codesourcery dot com" 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/msg02716.txt.bz2 ------- Comment #21 from joseph at codesourcery dot com 2009-12-29 21:44 ------- Subject: Re: gcc 4.4.0 error at postreload.c:396 On Tue, 29 Dec 2009, bonzini at gnu dot org wrote: > True, it is P5 but it is not invalid. Andreas, if you want to close this as > invalid you should first follow the target deprecation process and propose to > remove the target for 4.6. It is not a question of deprecation. There is no m68k-amigaos support in FSF GCC and I don't think there ever has been. Thus the submitter is using a version of GCC with an unknown set of third-party modifications. They should report any bugs to the provider of that modified version of GCC. That provider should determine whether the bugs are present in unmodified FSF GCC for some m68k-* target supported by FSF GCC, and pass on the reports to GCC Bugzilla (referencing the target supported by FSF GCC) if so. The bug reporting instructions are quite explicit that bugs in non-FSF versions of GCC do nto go here. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40414