Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcuq2-0001jI-CM for pgsql-bugs@arkaria.postgresql.org; Mon, 17 Jun 2019 16:50:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hcuq1-00005i-5m for pgsql-bugs@arkaria.postgresql.org; Mon, 17 Jun 2019 16:50:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcuq0-00005b-OP for pgsql-bugs@lists.postgresql.org; Mon, 17 Jun 2019 16:50:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hcupy-0005MI-9f for pgsql-bugs@lists.postgresql.org; Mon, 17 Jun 2019 16:50:31 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x5HGoMDw008750; Mon, 17 Jun 2019 12:50:22 -0400 From: Tom Lane To: Andres Freund cc: YunQiang Su , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build In-reply-to: <20190617163207.kgi5m4v2g2m252t5@alap3.anarazel.de> References: <15844-8f62fe7e163939b3@postgresql.org> <15052.1560455595@sss.pgh.pa.us> <23287.1560655935@sss.pgh.pa.us> <25321.1560659282@sss.pgh.pa.us> <22615.1560701813@sss.pgh.pa.us> <20190617163207.kgi5m4v2g2m252t5@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 17 Jun 2019 09:32:07 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8748.1560790222.1@sss.pgh.pa.us> Date: Mon, 17 Jun 2019 12:50:22 -0400 Message-ID: <8749.1560790222@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > I think we're pretty much at the point where we should just rip out all > of our own spinlock implementations for non-common platforms, and solely > rely on compiler intrinsics... The open coded ASM really doesn't age > very well, and there's very little chance of us actually testing them > properly. It's completely not true that this code isn't tested; we have two different MIPS buildfarm machines that surely exercise spinlocks plenty. (There's a separate argument to be had about whether we should drop source-code support for platforms that aren't represented in the buildfarm. I'm not inclined to, but you could tenably hold that position.) As for compiler intrinsics, I dunno. I don't have very much faith in the quality of those for non-mainstream platforms, either --- see https://www.postgresql.org/message-id/flat/25414.1483076673%40sss.pgh.pa.us for a not-too-old example. And a lot of platforms like this are running pretty old compilers, so even if the problems have been fixed it'll be a long time before we can depend on that. regards, tom lane