From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29329 invoked by alias); 13 Dec 2003 18:49:25 -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 29322 invoked from network); 13 Dec 2003 18:49:25 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 13 Dec 2003 18:49:25 -0000 Received: by zenia.home (Postfix, from userid 5433) id E0DB820766; Sat, 13 Dec 2003 13:46:40 -0500 (EST) To: Mark Kettenis Cc: gdb@sources.redhat.com Subject: Re: [RFC] i386 SSE registers References: <200312121706.hBCH6mIh011419@elgar.kettenis.dyndns.org> From: Jim Blandy Date: Sat, 13 Dec 2003 18:49:00 -0000 In-Reply-To: <200312121706.hBCH6mIh011419@elgar.kettenis.dyndns.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-12/txt/msg00191.txt.bz2 I'm not sure I understand how the various options you list would appear to the user. It sounds like, in any proposal, the SSE registers would just have bogus values when they're not available. Is there some way that the SSE regs could instead cease to exist (i.e. "print $xmm0" would give you a void value, 'info regi sse' would give you an error message)? Or is there some other non-invasive behavior which would make it clearer to the user what was going on?