From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17551 invoked by alias); 13 Sep 2002 01:43:46 -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 17537 invoked from network); 13 Sep 2002 01:43:45 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 13 Sep 2002 01:43:45 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g8D1R8w07730; Thu, 12 Sep 2002 21:27:08 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g8D1hhd14070; Thu, 12 Sep 2002 21:43:43 -0400 Received: from greed.delorie.com (hell.sfbay.redhat.com [172.16.27.25]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g8D1hfC22675; Thu, 12 Sep 2002 18:43:41 -0700 Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id g8D1hdg03001; Thu, 12 Sep 2002 21:43:39 -0400 Date: Thu, 12 Sep 2002 18:43:00 -0000 Message-Id: <200209130143.g8D1hdg03001@greed.delorie.com> From: DJ Delorie To: ac131313@ges.redhat.com CC: binutils@sources.redhat.com, gdb@sources.redhat.com In-reply-to: <3D813B07.4090401@ges.redhat.com> (message from Andrew Cagney on Thu, 12 Sep 2002 21:10:31 -0400) Subject: Re: New binutils directory src/include/cpu/ for .cpu and .opc files? References: <3D813B07.4090401@ges.redhat.com> X-SW-Source: 2002-09/txt/msg00136.txt.bz2 > I'd like to propose a new directory: > > src/include/cpu/ > > The directory would contain the CGEN .cpu and .opc input files used to > generate CGEN based binutils disassemblers, assemblers and (?) > relocations. GDB could also use these files when generating CGEN based > simulators. They aren't really include files, they're *source* files. Shouldn't they go in one of the source directories? I really don't think we want to go down the slippery slope of using include as a catch-all. Perhaps the opcodes directory would be a better choice?