From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29312 invoked by alias); 17 Oct 2010 08:01:50 -0000 Received: (qmail 29302 invoked by uid 22791); 17 Oct 2010 08:01:49 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,TW_EG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 17 Oct 2010 08:01:45 +0000 Received: (qmail 29482 invoked from network); 17 Oct 2010 08:01:43 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Oct 2010 08:01:43 -0000 From: Pedro Alves To: "H.J. Lu" Subject: Re: PATCH: gdbserver: Clear regcache if buf is NULL Date: Sun, 17 Oct 2010 08:01:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.33-29-realtime; KDE/4.4.2; x86_64; ; ) Cc: gdb-patches@sourceware.org References: <20100203174414.GA29948@lucon.org> <201010162149.36890.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201010170901.39736.pedro@codesourcery.com> 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-10/txt/msg00269.txt.bz2 On Saturday 16 October 2010 23:02:27, H.J. Lu wrote: > > Does that sound good? Or do you think keep using 0 would > > be better in this case? > > > > Values in vector registers are invalid, not unavailable. OS > initializes them to zero when they are set the firs time in > a program. I prefer *value not valid". Ah, yes, agreed. Okay, that's a different state from the "unavailable" in traceframe's (which really means the register exists, and its value also exists, but hasn't been collected by the tracepoint actions, so we don't know what it was). I'll adjust my patches to keep using 0 for now in cases like the vector case we're discussing then. Thanks! > GDB may update vector registers before they are set by program. > GDB sets proper bits in XSAVE area to tell OS/hardware that vector > registers now have valid values. -- Pedro Alves