Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751279AbdILDTt (ORCPT ); Mon, 11 Sep 2017 23:19:49 -0400 Received: from mail-yw0-f177.google.com ([209.85.161.177]:35953 "EHLO mail-yw0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751022AbdILDTs (ORCPT ); Mon, 11 Sep 2017 23:19:48 -0400 X-Google-Smtp-Source: ADKCNb6HlhnMMHOEVbSZMAt28BKJUiqPIYzpEGINz5eRZ0RdXuFttH7n+JV4xyMtZWxF3W61X652gPWoScsmaYL11G8= MIME-Version: 1.0 In-Reply-To: References: <20170910183150.GA2172@roeck-us.net> From: Max Filippov Date: Mon, 11 Sep 2017 20:19:46 -0700 Message-ID: Subject: Re: xtensa compiler error triggered by 'locking/lockdep: Implement the 'crossrelease' feature' To: Guenter Roeck Cc: Byungchul Park , Peter Zijlstra , LKML , Chris Zankel , "linux-xtensa@linux-xtensa.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v8C3K6Yf019387 Content-Length: 1178 Lines: 29 On Sun, Sep 10, 2017 at 6:58 PM, Max Filippov wrote: > On Sun, Sep 10, 2017 at 11:31 AM, Guenter Roeck wrote: >> xtensa:allmodconfig fails to build in mainline with compiler errors >> as follows. >> >> drivers/staging/rtl8723bs/core/rtw_ap.c: In function ‘expire_timeout_chk’: >> drivers/staging/rtl8723bs/core/rtw_ap.c:442:1: internal compiler error: >> in change_address_1, at emit-rtl.c:2126 >> >> drivers/staging/rtl8188eu/core/rtw_ap.c: In function ‘expire_timeout_chk’: >> drivers/staging/rtl8188eu/core/rtw_ap.c:445:1: internal compiler error: >> in change_address_1, at emit-rtl.c:2150 >> >> I tried gcc 6.3, 6.4, and 7.2; they all have the same problem. >> >> Bisect points to commit b09be676e0f ("locking/lockdep: Implement the >> 'crossrelease' feature"). >> >> The compile error is still seen if I disable CONFIG_LOCKDEP_CROSSRELEASE. >> The image builds fine if I disable both CONFIG_RTL8723BS and CONFIG_R8188EU. > > Thanks for the report. I'll look at the compiler. There was a bug in the xtensa gcc backend, now fixed. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82181 -- Thanks. -- Max