From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27593 invoked by alias); 23 May 2012 15:22:13 -0000 Received: (qmail 27578 invoked by uid 22791); 23 May 2012 15:22:12 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-vb0-f41.google.com (HELO mail-vb0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 May 2012 15:21:59 +0000 Received: by vbbey12 with SMTP id ey12so6026894vbb.0 for ; Wed, 23 May 2012 08:21:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=BxvgsZQ5rhqHuBsujPjp8OJWq/8jCAXk+9YSmijZaus=; b=k9dKjbJ9/+snsQis5B53ErHg0G19YXp33ajq+XyKCJ8unb4MTyiqj9bXd19nrW24Da X/3uhcOA7z+W6GRUZFAqF9spjZBs/rg5uwnz7h8wKjsJW7zLBh/kmEp231F/th/p79Kg LR7evhvfaxjrvW3yR9a/uxoW1+BWgLkyFTTOAdsINEgEPLhqe/7rHMD5CEGFUtvBNACW 4HigTMHbsW/w5l1XBSgrcVWowXuiT+TQjpkBMYtlTEslFPqeIZvu38wyjLrDuB704AzW KSF0ZoGu7LQHAnfZIZDw+lsh7dxHPWF1ZE+H5/zoNZahjHq64sEQMfcEqLlbavpuEUEU 7CoQ== Received: by 10.52.28.244 with SMTP id e20mr12728514vdh.14.1337786519036; Wed, 23 May 2012 08:21:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.28.244 with SMTP id e20mr12728503vdh.14.1337786518949; Wed, 23 May 2012 08:21:58 -0700 (PDT) Received: by 10.52.172.166 with HTTP; Wed, 23 May 2012 08:21:58 -0700 (PDT) In-Reply-To: <4FBBBF75.4040605@redhat.com> References: <1337697398-25866-1-git-send-email-guitton@adacore.com> <4FBBA8C8.4030909@redhat.com> <20120522152459.GQ51051@adacore.com> <4FBBBF75.4040605@redhat.com> Date: Wed, 23 May 2012 15:22:00 -0000 Message-ID: Subject: Re: [RFC] setting the raw content of a register From: Doug Evans To: Pedro Alves Cc: Jerome Guitton , gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQnfUedr4wFYTbtRPoXWnLDlQKVFdApveP1VUkY0x5Tomh9yrQf+TrMlvgv18wxdNVcXgRAH/gIvK/REhzWDc6Vjvvwbhu9jg4fL87s3nQAzQZGYnSz34g+n/uSfLCO/NzcYkdNdhnEXIW/YZIXXjIvnjm6IpQ== 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: 2012-05/txt/msg00896.txt.bz2 On Tue, May 22, 2012 at 9:31 AM, Pedro Alves wrote: > On 05/22/2012 04:24 PM, Jerome Guitton wrote: > >> Pedro Alves (palves@redhat.com): >> >>> What about : >>> >>> =A0 p $f14 =3D {double} {0xFFF0000000000050} >> >> I've been testing with a bareboard PPC, and this needs malloc; > > > Hmm, looks like you're right. =A0I was almost certain there was a way > to avoid the malloc if the cast/conversion is done to a type of > the exact same size as the source array, but it's escaping me now > how. IWBN to solve this without adding a new command, the problem is more general than just assigning values to registers. I may want to use the value in an expression, for example.