From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2481 invoked by alias); 7 Feb 2010 23:03:19 -0000 Received: (qmail 2098 invoked by uid 22791); 7 Feb 2010 23:03:17 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ww0-f41.google.com (HELO mail-ww0-f41.google.com) (74.125.82.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 07 Feb 2010 23:03:12 +0000 Received: by wwb22 with SMTP id 22so939175wwb.0 for ; Sun, 07 Feb 2010 15:03:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.162.142 with SMTP id y14mr1327397wek.192.1265583789769; Sun, 07 Feb 2010 15:03:09 -0800 (PST) In-Reply-To: <6dc9ffc81002071425y74b5bb8eha47bacc6f1d2a33e@mail.gmail.com> References: <20100205011447.GA28263@lucon.org> <201002072152.o17LqEm7030005@glazunov.sibelius.xs4all.nl> <6dc9ffc81002071400u5bad1726v93330aeb38246143@mail.gmail.com> <20100207221444.GA5399@caradoc.them.org> <6dc9ffc81002071425y74b5bb8eha47bacc6f1d2a33e@mail.gmail.com> Date: Sun, 07 Feb 2010 23:03:00 -0000 Message-ID: <6dc9ffc81002071503r79077130meb9f66a6cf51ed09@mail.gmail.com> Subject: Re: PATCH: PATCH: Add builtin floating point types From: "H.J. Lu" To: "H.J. Lu" , Mark Kettenis , gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-02/txt/msg00195.txt.bz2 On Sun, Feb 7, 2010 at 2:25 PM, H.J. Lu wrote: > On Sun, Feb 7, 2010 at 2:14 PM, Daniel Jacobowitz = wrote: >> On Sun, Feb 07, 2010 at 02:00:36PM -0800, H.J. Lu wrote: >>> Is there a way to call i387_ext_type from =A0target-descriptions.c? >>> Otherwise, =A0XML target description will create multiple i386_ext >>> types and won't work for x86 since x86 requires single i386_ext >>> type per arch. >> >> Maybe the common code could cache the created types? >> > > I need a place to hold the created type in the common code. > When do I put it? > How about adding it to common code without initializing it? I will lazy initialize it in target-description.c only when it is used? Thanks. --=20 H.J.