From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20816 invoked by alias); 5 Aug 2003 04:27:31 -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 20808 invoked from network); 5 Aug 2003 04:27:30 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 5 Aug 2003 04:27:30 -0000 Received: from drow by nevyn.them.org with local (Exim 4.20 #1 (Debian)) id 19jtPz-0003e4-Sw for ; Tue, 05 Aug 2003 00:27:27 -0400 Date: Tue, 05 Aug 2003 04:27:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: Allow C++ or C99 in sim/*? Message-ID: <20030805042727.GA13980@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <3F2B02B8.3020906@redhat.com> <3F2F31B6.3060900@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F2F31B6.3060900@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-08/txt/msg00055.txt.bz2 On Tue, Aug 05, 2003 at 12:25:26AM -0400, Andrew Cagney wrote: > Two parts, and two features, come to mind: > > - the sim-endian code which, I think, would work better using templates > > - the h/w devices which are objects with virtual methods > > I suspect a careful choice of language features will avoid the > performance problems - no multiple inheritance for instance. > > after that, well who knows. At which point, it seems, you're redesigning sid rather than sim? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer