From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29237 invoked by alias); 18 Jun 2004 19:29:06 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29230 invoked from network); 18 Jun 2004 19:29:05 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 18 Jun 2004 19:29:05 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i5IJT5e3015751 for ; Fri, 18 Jun 2004 15:29:05 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i5IJT4027551; Fri, 18 Jun 2004 15:29:05 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 97F222B9D; Fri, 18 Jun 2004 15:28:52 -0400 (EDT) Message-ID: <40D34274.50803@gnu.org> Date: Fri, 18 Jun 2004 19:29:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: Post GDB 6.2, require new frame code Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00199.txt.bz2 GDB's new frame infrastructure was introduced more than a year ago (dwarf2-frame added May '03) and then included in the 6.0 and 6.1 releases. Since that introduction, we've seen: alpha ARM AVR CRIS d10v FRV PA-RISC i386 ia64 m32r m68hcll m68k m88k mips ppc s390 sh4 sparc vax all updated to this new framework. Unfortunately, though, we're still left with a few architectures relying on the old framework. We're now faced with the problem of what to do with the remaining architectures. The choices I see are: - continue to support the legacy framework - convert the remaining architectures - phase out the remaining architectures So as to avoid the problem of this dragging on indefinitely, we need to establish a clear schedule by which all architectures are expected to have been updated. To that end: - make GDB 6.2 the last release to support the legacy frame code - in 6.2 NEWS, list unconverted architectures as about to be obsoleted - Post 6.2 release, obsolete any remaining architectures comments, Andrew