From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37871) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2HN-0001yH-13 for qemu-devel@nongnu.org; Tue, 01 Oct 2013 11:54:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VR2HE-0003gj-Js for qemu-devel@nongnu.org; Tue, 01 Oct 2013 11:54:28 -0400 Received: from mail-yh0-x234.google.com ([2607:f8b0:4002:c01::234]:38971) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VR2HE-0003gY-Fo for qemu-devel@nongnu.org; Tue, 01 Oct 2013 11:54:20 -0400 Received: by mail-yh0-f52.google.com with SMTP id i7so187934yha.39 for ; Tue, 01 Oct 2013 08:54:20 -0700 (PDT) Sender: Richard Henderson Message-ID: <524AF027.1020701@twiddle.net> Date: Tue, 01 Oct 2013 08:54:15 -0700 From: Richard Henderson MIME-Version: 1.0 References: <1379945085-29086-1-git-send-email-rth@twiddle.net> <1379945085-29086-8-git-send-email-rth@twiddle.net> <5249BF37.50000@suse.de> <5249D57E.2040003@twiddle.net> <524AEFA0.70006@suse.de> In-Reply-To: <524AEFA0.70006@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 07/10] target-s390: Fix STIDP List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel@nongnu.org On 10/01/2013 08:52 AM, Alexander Graf wrote: > On 09/30/2013 09:48 PM, Richard Henderson wrote: >> On 09/30/2013 11:13 AM, Alexander Graf wrote: >>>> - int cpu_num; >>>> + union { >>>> + uint64_t cpuid; >>>> + struct { >>>> +#ifdef HOST_WORDS_BIGENDIAN >>>> + uint32_t cpu_num; >>>> + uint32_t machine_type; >>>> +#else >>>> + uint32_t machine_type; >>>> + uint32_t cpu_num; >>>> +#endif >>> Are we guaranteed that we don't need to pack? Also anonymous unions/structs are >>> a gcc extension IIRC. And why do you swap endianness here, but not above when >>> defining the machine_type value? >> (1) I can't imagine that we would; such struct/unions are used all over. > > *shrug* you're the expert :). > >> (2) Sure, but we've so many other gcc extensions I figured it didn't matter. > > Avi complained about it to me in Linux patches. Not sure how much we care in QEMU. > >> (3) Of course. I want host endianness, not target endianness. > > Phew. I think I'm slowly starting to grasp what you're trying to do here. Any > way you could make this more explicit through shifts and ors and other explicit > operations? This feels like too much magic to "just understand on a glimpse" to > me. Yes, I could arrange for it to be two loads and assembled at runtime. It's not like this insn is used on any hot path... or indeed, apparently more than once in the whole lifetime of the system. r~