From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv5d9-0001oK-13 for qemu-devel@nongnu.org; Mon, 23 Dec 2013 08:33:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vv5cz-00055Y-86 for qemu-devel@nongnu.org; Mon, 23 Dec 2013 08:33:10 -0500 Received: from v220110690675601.yourvserver.net ([37.221.199.173]:38382) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv5cz-00055B-26 for qemu-devel@nongnu.org; Mon, 23 Dec 2013 08:33:01 -0500 Message-ID: <52B83B87.8020404@weilnetz.de> Date: Mon, 23 Dec 2013 14:32:55 +0100 From: Stefan Weil MIME-Version: 1.0 References: <20131223115622.GA6490@redhat.com> <52B831AC.8030207@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] target-arm: fix build on fedora List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Paolo Bonzini Cc: John Rigby , "Michael S. Tsirkin" , QEMU Developers , Alexander Graf , Laszlo Ersek , Richard Henderson Am 23.12.2013 13:59, schrieb Peter Maydell: > On 23 December 2013 12:50, Paolo Bonzini wrote: >> Il 23/12/2013 13:37, Peter Maydell ha scritto: >>> At a minimum, if we take this approach we should add TODO comments >>> to the effect that the NULL terminator and the if() can be removed >>> when the first real AArch64 CPU is added. >>> >>> I think I'd rather put the if (!info->name) continue into the function >>> which is doing the looping over the array. >> Or just change the termination condition from a check on the array size >> to one on info->name. > That would take it out of line with the equivalent 32 bit ARM code > (and also moxie and openrisc for what little that's worth) and be > fractionally more tedious to revert later. > > thanks > -- PMM What about adding a dummy CPU (which can be removed later)? I also got a warning here when I used cgcc / smatch recently, but did not send a patch because there are too many possible fixes and none of them seemed to be elegant :-) Nevertheless, here is one of them: --- a/target-arm/cpu64.c +++ b/target-arm/cpu64.c @@ -46,6 +46,11 @@ static void aarch64_any_initfn(Object *obj) set_feature(&cpu->env, ARM_FEATURE_V7MP); set_feature(&cpu->env, ARM_FEATURE_AARCH64); } +#else +static void aarch64_dummy_initfn(Object *obj) +{ + hw_error("Dummy CPU not supported"); +} #endif typedef struct ARMCPUInfo { @@ -57,6 +62,9 @@ typedef struct ARMCPUInfo { static const ARMCPUInfo aarch64_cpus[] = { #ifdef CONFIG_USER_ONLY { .name = "any", .initfn = aarch64_any_initfn }, +#else + /* TODO: Dummy CPU to avoid empty array. Fix when a real CPU is added. */ + { .name = "dummy", .initfn = aarch64_dummy_initfn }, #endif }; Of course, any other fix is also okay. Cheers and Merry Christmas Stefan