From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3CBFC47DD9 for ; Wed, 28 Feb 2024 12:23:03 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 2F80B6B0075; Wed, 28 Feb 2024 07:23:03 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 2A7C16B009C; Wed, 28 Feb 2024 07:23:03 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 196A66B009D; Wed, 28 Feb 2024 07:23:03 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 077A96B009C for ; Wed, 28 Feb 2024 07:23:03 -0500 (EST) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id BF288A12DE for ; Wed, 28 Feb 2024 12:23:02 +0000 (UTC) X-FDA: 81841127004.11.0B2EEFC Received: from elvis.franken.de (elvis.franken.de [193.175.24.41]) by imf06.hostedemail.com (Postfix) with ESMTP id D0E4F180015 for ; Wed, 28 Feb 2024 12:23:00 +0000 (UTC) Authentication-Results: imf06.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf06.hostedemail.com: domain of tsbogend@alpha.franken.de designates 193.175.24.41 as permitted sender) smtp.mailfrom=tsbogend@alpha.franken.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1709122981; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2hDdbTE1LW42Tq/N9VIrZc7iwwYGneyw8c5uOXVBDWk=; b=lfvGkbEcPgdLTyYcVbTLDIav04kQ2lYPnNys5OgC2o2D4arKdzc5NpkxuLDMd0hiMzq5Xs SNWcN0ITpHeYzs9MI88sqYzEcf3fGEXVBMrpo7tIrGLiCaS5vXKgLwYVZXZDvHA1zdAnXz 0OxkRUssJT+ZFb3XK7v4llxmwGfOTYs= ARC-Authentication-Results: i=1; imf06.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf06.hostedemail.com: domain of tsbogend@alpha.franken.de designates 193.175.24.41 as permitted sender) smtp.mailfrom=tsbogend@alpha.franken.de ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1709122981; a=rsa-sha256; cv=none; b=A1BGstyVUV5pzO71PXqkmQhMyX9eExN/+gUFAXwcY/hUT3SMBOPa3WJdkIBREbP5WW9n74 boDQhwvSNDfIUFAU9DyuIfSFeRr+SzbijEYU5xp5zniZCigdXSLInvNBxpQDXO5ivAlCsp lULA68XPUKm2gI8wa2/4KD5YarVRz4A= Received: from uucp by elvis.franken.de with local-rmail (Exim 3.36 #1) id 1rfIxd-0003al-00; Wed, 28 Feb 2024 13:22:57 +0100 Received: by alpha.franken.de (Postfix, from userid 1000) id 81A77C0267; Wed, 28 Feb 2024 12:26:58 +0100 (CET) Date: Wed, 28 Feb 2024 12:26:58 +0100 From: Thomas Bogendoerfer To: Jiaxun Yang Cc: oe-kbuild-all@lists.linux.dev, Linux Memory Management List , kernel test robot , "linux-mips@vger.kernel.org" Subject: Re: parse_r register name (was: [linux-next:master 9092/10236] arch/mips/kernel/mips-mt.c:3207: Error: Unable to parse register name $fp) Message-ID: References: <202402270524.HtRvZbPR-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspam-User: X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: D0E4F180015 X-Stat-Signature: i49erimeofiethkt69aznf9mkxm66hx8 X-HE-Tag: 1709122980-215092 X-HE-Meta: U2FsdGVkX18VYKmfRKytNdersDtxA/fYGLw1MNdWE7U2bQXIJpyyd42R6V3O4NgTeWdxeDlPaguHtywgquZar4SWEysEhia036XjNoWjW8EJHeUmPUoEhZgNC84oMkiY8gkFDCX2NWTqWtmswF2Ie2f/RLBLvXtFRyUt8kk44ffGaX0GU3e2tRHNJeybt1cNSBQDCOmgdiGEuQUYcRqChR3MrD6XnE41S2JfXtPJBlUBgohcfGHR3jS8ZNL8oJ04NggkWIZ32HY80huREc+AqKcaWVDte7IAeguyVdWk5O1tEGVln3U2tlg3lfBEdyBjC7RTLJRpNrjtZGjUAreLaGCZYkhUi0a2WsYh5mIH6pQaiub8IS+adjS3Znqbli96WCEGMJdMo9vMY10OD3jNClVxFVpuP9qp7luaqHFhhxdOjogNcw7O8nkfyPJOGeeMqIMVb+gcr1T4qaRRa2GCQpTP2/QArkiHGMSCR2SM1qGoUKnhE6uGRThtaM241VJjAJvTPFsa+5byFm/Rc4sEtQmbB/9zmcNCvh/z240T3O6WQCTOcFHhKNFSLEZlYpA35yzq3e65kKGRaKtARTaUR28A9jNtJeckM/3larulYSnRxODDDOFdfev+bK+qgYuA5C5rbv5wil3bhYh1coXCzAxMQi7Qcf3TIukWtenm1qFYW3cv5Gt78zbKpvX8pOfK80l9M37gTp7NpcSPzCnPUm9FVbn9zyz6LzDbmnZgHkCjQMiXeXCtQLf8UTCl99S12QxptFH0hqYka/csUokBC5ZI8/5GQ0J3AyPe+Nh+3/+umMZB8cizR7nIC5XBesiMURb22QGCYJDzL8T2WIG/AiJB81vb0x0wHIQVIZYSZHg= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000214, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Tue, Feb 27, 2024 at 07:22:24PM +0000, Jiaxun Yang wrote: > (Top posting for visibility) > We had a discussion on this issue[1], the conclusion was it's a clang > misbehavior, > however, it turns out that GCC is doing the same. > > Do you want to pick that patch? applied to mips-next. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]