From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Sun, 19 Oct 2014 19:51:18 +0100 Subject: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 In-Reply-To: References: <543EF2B6.1050009@hurleysoftware.com> <20141016001801.GQ12379@n2100.arm.linux.org.uk> <20141017134112.GS12379@n2100.arm.linux.org.uk> <20141019095555.GU12379@n2100.arm.linux.org.uk> Message-ID: <20141019185118.GA22014@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, Oct 19, 2014 at 08:55:14AM -0700, Linus Torvalds wrote: > On Oct 19, 2014 2:56 AM, "Russell King - ARM Linux" > wrote: > > > > Right, with the test fixed (&& instead of ||), I've just pushed it out > > this morning, and received the results from Olof's kernel builder, > > which shows that he's using a gcc 4.8.x version which gets caught by > > the test. > > > > I think Olof needs to do something about his gcc version there. > > ... or maybe you could just add a "I have a working compiler" config option > override to show people to say "I have one of the affected versions, but my > compiler has the fix"? Does that work for things like allnoconfig and randconfig? I guess people /could/ seed those appropriately, but that seems to be something that Olof wants to avoid doing. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net.