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 1guf3n-0004ZF-Oo for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Feb 2019 15:05:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1guf3m-0002Vx-Dm for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Feb 2019 15:05:50 +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 1guf3m-0002Si-1n for pgsql-hackers@lists.postgresql.org; Fri, 15 Feb 2019 15:05:50 +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 1guf3j-0002fE-GJ for pgsql-hackers@lists.postgresql.org; Fri, 15 Feb 2019 15:05:48 +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 x1FF5cEN000987; Fri, 15 Feb 2019 10:05:38 -0500 From: Tom Lane To: Alvaro Herrera cc: Kyotaro HORIGUCHI , andres@anarazel.de, thomas.munro@enterprisedb.com, andrew@tao11.riddles.org.uk, david.rowley@2ndquadrant.com, pgsql-hackers@lists.postgresql.org Subject: Re: Using POPCNT and other advanced bit manipulation instructions In-reply-to: <20190215144123.GA31671@alvherre.pgsql> References: <20190215144123.GA31671@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 15 Feb 2019 11:41:23 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <985.1550243138.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 15 Feb 2019 10:05:38 -0500 Message-ID: <986.1550243138@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > Ah, I understand it now: > https://stackoverflow.com/questions/25683690/confusion-about-bsr-and-lzc= nt/43443701#43443701 > if you call LZCNT/TZCNT on a CPU that doesn't support it, it won't raise > SIGILL or anything ... it'll just silently compute the wrong result. > That's certainly not what I call a fallback! Yeah, that's pretty nasty; it means there's no backstop for whether your choose function gets it right :-( Is POPCNT any better in this respect? regards, tom lane