From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25746 invoked by alias); 4 May 2003 03:12:41 -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 25730 invoked from network); 4 May 2003 03:12:39 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 4 May 2003 03:12:39 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D7CF62B2F for ; Sat, 3 May 2003 23:12:38 -0400 (EDT) Message-ID: <3EB48526.9060104@redhat.com> Date: Sun, 04 May 2003 03:12:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: -frame.c, frame/.c, config//frame.c, ... Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-05/txt/msg00030.txt.bz2 This picks up an old old topic Since MarkK is threatening to get the i386 using the new frame code, now is probably the time to think about where all these frame modules should live: d10v-frame.[hc]: Fills the top-level directory up with more stuff. That got objections when it was last suggested. frame/.[hc]: Keeps all the frame code in one directory. This makes it clearer that the code is ment to be frame centric (and not the place to put non-frame stuff). config//frame.[hc]: Keeps the cpu stuff in a single directory. ...: ... ... (there is a long standing task of restructuring the code base, might as well start here :-) Andrew