From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23831 invoked by alias); 22 Jul 2004 02:09:01 -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 23809 invoked from network); 22 Jul 2004 02:08:55 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org with SMTP; 22 Jul 2004 02:08:55 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 5272347D91; Wed, 21 Jul 2004 19:08:54 -0700 (PDT) Date: Thu, 22 Jul 2004 02:09:00 -0000 From: Joel Brobecker To: gdb-patches@sources.redhat.com Subject: Re: [RFA] mips-irix SEGV: long doubles are 128 bits long on IRIX Message-ID: <20040722020854.GT1278@gnat.com> References: <20040721212522.GP1278@gnat.com> <20040721212930.GA21706@nevyn.them.org> <20040721233310.GR1278@gnat.com> <20040722003951.GA26928@nevyn.them.org> <20040722004640.GS1278@gnat.com> <20040722004808.GB27215@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040722004808.GB27215@nevyn.them.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-07/txt/msg00301.txt.bz2 > According to GCC long double is 128-bit for all n64 and n32 targets. OK. So I am planning on setting the size to 128-bit for the following ABIs, is this the correct list: . O64 (??? Didn't see any mention of this in the IRIX man pages) . EABI32, EABI64 . N32/N64 I will add the same set_gdbarch_...() call in each section of the case statement on mips_abi. Would that be the correct patch? I am making extra sure before doing the testing because running the testsuite takes several hours even after my fixes (it was even worse before, it was taking 9-10 hours, and I think this is because of bugs in expect/dejagnu that don't detect when the debugger dies or when the debugger expects an answer from the user after having reported an internal error - I just don't want to go there and fix the problems in GDB instead). And to make things worse, the run sometimes get screwed up for some reason I don't understand. So I want to do the testing overnight if I can and try to avoid any unecessary run. Thanks, -- Joel