Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp382226imm; Thu, 26 Jul 2018 21:46:49 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcTTKZRX1LmaaM6Ewp1xW0mWSSU/ieLxIR2Fnn96foOHK9Y7BjJ8cJyDh2QHiyqF3j7m7P+ X-Received: by 2002:a62:34c4:: with SMTP id b187-v6mr4982409pfa.15.1532666809792; Thu, 26 Jul 2018 21:46:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532666809; cv=none; d=google.com; s=arc-20160816; b=rcVOBfZEZKUtYWB7iGU9yfWPo//uWqpBLQlOZXa4aOUSe2NHAMAe7H7SdG/ciExRPX zhrfwnP/yjZw1g8Cu/IWCFEFRsJW8t9jrGAF8L7Zsv+esQFWGT651ECUwXFblYht+im1 vGiTODhwmXhwEj3N8Gn42pxET5ISzfT7zFa85v4UMiANFugtEqatGv1wkOQaM7Aimk+q pCjX2/ThVfxWsTVOqr3HR23co9zl/p6RaKIah9nqAqBw/KjJsPZdlpqC9RLwAIagt7g9 iEAWMcXJMVVTfbzCqXbTK+sAts7NI/GiP0p4ERC7zykh0FiNnF+cMF2SBnvZX0k+nvkk NBUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:message-id :in-reply-to:subject:cc:to:from:date:arc-authentication-results; bh=pWrEXxBG9tzum4pq95JwtDQv2uaq971tIXc8Du79AOY=; b=Ctkaw2fqVaio3/w4BeZ/aJ6yIIsNi6/F4w3MHw4wFoSfIYra6jZbJbdnaEv43D8xYU WiRm4nB5coX5FQyLz2OsdPjWZ2EtA2Txko/LQhrcRVA1duXBNgZKwdpaaVK2Zkxfa8fk l4S5umaB7LAdX0iiiw2yMC0++KHXgVVbON6gjHSrTExygyisQ+jOXXbjUlLVZSLpai31 cYgGhiOul9dL1d9G1CoY3WWruNHmx9scekPct3chAbFlKOg2TIyj7i669ZHoRogMshI6 BFPb4lEuSwgawLdFxdhGgYOisTCogoFOiBuiPODrIMOjsA+dSzMjfxluqTE7kl23xdOS abtQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 62-v6si3417586pfu.79.2018.07.26.21.46.35; Thu, 26 Jul 2018 21:46:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729448AbeG0GEK (ORCPT + 99 others); Fri, 27 Jul 2018 02:04:10 -0400 Received: from kvm5.telegraphics.com.au ([98.124.60.144]:48672 "EHLO kvm5.telegraphics.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725999AbeG0GEJ (ORCPT ); Fri, 27 Jul 2018 02:04:09 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by kvm5.telegraphics.com.au (Postfix) with ESMTP id 45D1F29532; Fri, 27 Jul 2018 00:44:06 -0400 (EDT) Date: Fri, 27 Jul 2018 14:44:17 +1000 (AEST) From: Finn Thain To: Randy Dunlap cc: Andreas Schwab , LKML , Geert Uytterhoeven , linux-m68k@lists.linux-m68k.org Subject: Re: m68k allmodconfig build errors In-Reply-To: <761399f0-0b10-716c-1e80-cfb19c06e455@infradead.org> Message-ID: References: <28ebe45d-3dbd-2a82-f537-b0725f7a2bcf@infradead.org> <878t66idai.fsf@igel.home> <94dc0357-10d4-c3dc-ef2a-9643f08d2a09@infradead.org> <761399f0-0b10-716c-1e80-cfb19c06e455@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 Jul 2018, Randy Dunlap wrote: > > > > The untested patch below may work. It seems that it may be relevant to > > both arc and m68k: > > > I got back to looking at the build errors. I agree with Andreas that > all of the fields in question are null-terminated, so Finn's patch looks > good to me. > > That patch is insufficient: ERROR: "strcmp" [fs/hfsplus/hfsplus.ko] undefined! And I haven't even attempted "make ARCH=m68k ... allyesconfig" let alone "make ARCH=arc ... allyesconfig". And we have to anticipate an ongoing game of whack-a-mole here, as new library calls get added to linux and new optimizations get added to gcc. The real problem here seems to be a compiler bug: converting strncmp to strcmp is bogus. Some implicit assumptions in that code transformation: 1. that strcmp is equivalient to strncmp in this case 2. that strcmp is faster than strncmp in this case 3. that strcmp is actually available to the linker Why doesn't gcc convert strncmp to __builtin_strcmp? That would require fewer assumptions, and it would actually link, and we wouldn't have to keep patching things... --