From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22989 invoked by alias); 11 Jun 2005 01:40:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22978 invoked by uid 22791); 11 Jun 2005 01:40:35 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 11 Jun 2005 01:40:35 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j5B1eYTE015108 for ; Fri, 10 Jun 2005 21:40:34 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5B1eSO07256; Fri, 10 Jun 2005 21:40:28 -0400 Received: from [172.16.24.50] (bluegiant.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id j5B1eQml001837; Fri, 10 Jun 2005 21:40:27 -0400 Message-ID: <42AA410A.7070008@redhat.com> Date: Sat, 11 Jun 2005 01:40:00 -0000 From: Michael Snyder User-Agent: Mozilla Thunderbird (X11/20050322) MIME-Version: 1.0 To: Mark Kettenis CC: kevinb@redhat.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] Add support for Morpho ms1 processor References: <20050603172038.449a41b9@ironwood.lan> <200506102312.j5ANCoWe018703@elgar.sibelius.xs4all.nl> In-Reply-To: <200506102312.j5ANCoWe018703@elgar.sibelius.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg00103.txt.bz2 Mark Kettenis wrote: > Especially naming an enum `gdb_regnum' seems like > a bad idea to me. What's the E_-prefix trying to convey? I seem to > remember a few other embedded processors using the same E_-prefix for > their register names. Yeah, those were probably all mine. I started doing that a few years ago. The prefix was just to differentiate the enum from the macro -- avoid namespace pollution, you might say.