From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwZdT-0000jS-KV for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:06:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwZdS-0002Y2-Lv for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:06:19 -0400 Received: from e36.co.us.ibm.com ([32.97.110.154]:59977) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwZdS-0002Xu-AD for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:06:18 -0400 Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7PCxkpH027010 for ; Thu, 25 Aug 2011 06:59:46 -0600 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7PD6E8j111118 for ; Thu, 25 Aug 2011 07:06:14 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7PD6Dd9008432 for ; Thu, 25 Aug 2011 07:06:14 -0600 Message-ID: <4E5648C4.3000604@us.ibm.com> Date: Thu, 25 Aug 2011 08:06:12 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4E48BF2F.7080901@web.de> <4E501243.2090806@mail.berlios.de> <4E54C045.9020007@web.de> <4E562C38.3010908@web.de> <4E564254.2080204@web.de> In-Reply-To: <4E564254.2080204@web.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL] slirp: Fix issues with -mms-bitfields List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Blue Swirl , TeLeMan , qemu-devel On 08/25/2011 07:38 AM, Jan Kiszka wrote: > On 2011-08-25 14:02, TeLeMan wrote: >> On Thu, Aug 25, 2011 at 19:04, Jan Kiszka wrote: >>> What a mess. Do we really have to go through all 257 packed data structs >>> in QEMU and add these MS compat bits to all potentially affected ones? >> I prefer to detect -mms-bitfields and remove it in configure. > > /me too - if that is possible, ie. if the glib bits we are using doesn't > require us to apply that mode. Can anyone comment on this? So why can't we just #pragma guard all of the slirp bits? Why are we doing it on a per data structure basis? Regards, Anthony Liguori > > Jan >