From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe004.messaging.microsoft.com [216.32.180.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.global.frontbridge.com", Issuer "Microsoft Secure Server Authority" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 0E3702C0081 for ; Tue, 13 Nov 2012 08:51:22 +1100 (EST) Date: Mon, 12 Nov 2012 15:51:06 -0600 From: Scott Wood Subject: Re: Build regressions/improvements in v3.7-rc5 To: Geert Uytterhoeven In-Reply-To: (from geert@linux-m68k.org on Mon Nov 12 15:02:46 2012) Message-ID: <1352757066.32153.5@snotra> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 11/12/2012 03:02:46 PM, Geert Uytterhoeven wrote: > On Mon, Nov 12, 2012 at 9:58 PM, Geert Uytterhoeven > wrote: > > JFYI, when comparing v3.7-rc5 to v3.7-rc4[3], the summaries are: > > - build errors: +14/-4 >=20 > 14 regressions: > + drivers/virt/fsl_hypervisor.c: error: 'MSR_GS' undeclared (first > use in this function): =3D> 799:93 These reports would be more useful if the actual .config were provided, =20 rather than just saying "powerpc randconfig". I doubt this particular one is a regression; it looks like the =20 dependencies have always been too weak (patch sent) and you're just =20 comparing different randomly-generated configs. > powerpc-randconfig >=20 > + error: relocation truncated to fit: R_PPC64_REL24 against symbol > `._mcount' defined in .text section in arch/powerpc/kernel/entry_64.o: > (.text+0x1ff9eb8) =3D> (.text+0x1ffa274), (.text+0x1ff7840) >=20 > powerpc-allyesconfig It's been over 3 years since powerpc-allyesconfig built (it's just too =20 big for the relocation model the kernel uses) -- how is this a =20 regression? -Scott=