Re: Optimize Arm64 crc32c implementation in Postgresql

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Yuqi Gu <Yuqi(dot)Gu(at)arm(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimize Arm64 crc32c implementation in Postgresql
Date: 2018-04-04 12:00:14
Message-ID: CAEepm=0AH=z81xcciH37VCMKNhy7sxXn0eDJaL+FRdDV-z_VtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 4, 2018 at 11:47 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> BTW I did some googling just now and found out that some libraries use
> a technique they call "CPU probing": just try it and see if you get
> SIGILL. Is that a bad idea for some reason? Here is a quick hack --
> anyone got an ARM system without crc that they could test it on?

Hmm. I suppose there must be some horrendous non-portable 'step over
the instruction' bit missing in the signal handler. Probably not a
great idea.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-04-04 12:18:55 Re: Add default role 'pg_access_server_files'
Previous Message Nikhil Sontakke 2018-04-04 11:58:54 Re: [HACKERS] logical decoding of two-phase transactions