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 1haYqh-0001yy-Go for pgsql-bugs@arkaria.postgresql.org; Tue, 11 Jun 2019 04:57:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1haYqg-00078I-DO for pgsql-bugs@arkaria.postgresql.org; Tue, 11 Jun 2019 04:57:30 +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 1haYqg-00077a-1c for pgsql-bugs@lists.postgresql.org; Tue, 11 Jun 2019 04:57:30 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1haYqd-00063H-K8 for pgsql-bugs@lists.postgresql.org; Tue, 11 Jun 2019 04:57:28 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0BBA62246C; Tue, 11 Jun 2019 00:57:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 11 Jun 2019 00:57:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=D9GttopWke+lUKwEqJYMw4gJW6/ SHdYlHHtHdrpmHhw=; b=sJJYUniUcZsRFU5CcqSdmZsUNCBJ7N6THhQgn+JybxJ tCWuca5Waw7PONpU30yca6tEhEEXhKdKXaspVs9PYG9ntrys4WIIwZBwPuLGAsm+ /XXnNmW8E/4CC0oEX5WKzOfCWQJ0uVoiJibW3bqXgBdVzlikxhUaq0CecDibWEAA uMZ5L56MjP3DGXyAcgUweSyf8sqglIu+qgYO4I0Dj127QfzdBbZMPb4OLvCXLn2g yKdvjgyoGs2TSK0ICX7oJtQHkqsm5IYePRgZsQejEY6pMBS322TmVl4O8OYGSWLQ 9CH/001czTbbHdG8c2M9hPTehXbigsGUUaVIFMxLhUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=D9Gtto pWke+lUKwEqJYMw4gJW6/SHdYlHHtHdrpmHhw=; b=HqNrNXeFyc4wd2Kqq4OCUD sH6x7dFt96d2zpC9MkNGHXwfuTw6DgjX//WnELnyS9k4QN+q0pIyvP660qgq3VD/ iLIj+cZ54LovXcQOsBjxW8cFwhEXS5PAn0kTD/OpKAQRZRC1FgaSaT0GZkhMgRef oKwpbkqkTaO849hX3QHiC00izDqA1NxdBWP9T8+OivvWf/F9nmD15I6GaUOrn8Yt 9hYo2LQn4dkBpmbzwZbAsLlwlog+YNq4hk4t/T/OtZLPBaBlEqr8xrtOc3GtexPG FLNvHSuPZPD1NyBANJAFDfkwKkeoqFkrw5emXCYt8MHr7r/6jsPaieIgiMdw+QjA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehfedgkeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdlfeehmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucffohhmrghinhepph hoshhtghhrvghsqhhlrdhorhhgnecukfhppeduuddurddutddvrddukedtrddukeehnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiiine cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id D5D91380088; Tue, 11 Jun 2019 00:57:25 -0400 (EDT) Date: Tue, 11 Jun 2019 13:57:23 +0900 From: Michael Paquier To: wzssyqa@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15844: MIPS: remove .set mips2 in s_lock.h to fix r6 build Message-ID: <20190611045723.GC2132@paquier.xyz> References: <15844-8f62fe7e163939b3@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wULyF7TL5taEdwHz" Content-Disposition: inline In-Reply-To: <15844-8f62fe7e163939b3@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --wULyF7TL5taEdwHz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 11, 2019 at 04:39:35AM +0000, PG Bug reporting form wrote: > MIPS r6 changes the encoding of LL/SC instruction, > while the .set mips2 will force assembler to generate > old encoding. This is quite architecture-specific. May I suggest to add this patch to the follow-up commit fest for awareness: https://commitfest.postgresql.org/23/ Do you have any references, like documentation, which summarize that? -- Michael --wULyF7TL5taEdwHz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlz/NLMACgkQnvQgOdby QH1S2g/9GuipWOhQtDNL/Q+Uh1rkR9xv7JGoYEHsZsAU3t0rv0s8+xcEAJshm0jy Xgx2AmOTd8neqhQfSPio2Lg1F2oPhIf7Gd8Xz/UpiOeDa/7g+6DDyXdaJVAVTYt3 8U7c6+TKF1bM18gJljoaofwyr+ZnZLw5ds/2m4KCEiogs7zNOh9Ut0iBdndfgs7g hRydFh4adpLOarEOuQK44TY3+eLZBwipfKw3/Qj92w1ZgB9a0yNvBQ/fQnO254ep U76yZ/1GYEUCImHXz3YKTYCgn7kDKxZf5Z8ooGrEAmL6QFawZpzLT0da9QWWh0He Fhnk3skfM1p8B84N8cLR05wvNnmbymzbZAojzcQL66vuSMucr8yMFfM0DwNysDYU gtJxWA7rHwaVjBR3dhr483IDBAcLl/VEePA17qNKWPjqji7ghm0nMK9uC/ZIlVkL hqlmrGgP6q+nM1lJmhl/VBUNoENBIVH+A2eJdR4zHn2LihBwlX5OO6ty4VhWRkv0 +kT7ccvdWWppQbgSD8xlFQkt8J+HrDiuZJXSfmZ+atRLiw+QVD5uSlKSfHuZSkVw pIC6uJJEWQ6kTekohFOFhVPtlVb4OCwyHL3VtVz40F8NQjnhepP1QymfKrjG7ZbK o1hu7toJJo7WvWGnOo328GsNDo6X630Do9B5+kb2sGuN1RrB5hc= =nrz4 -----END PGP SIGNATURE----- --wULyF7TL5taEdwHz--