Re: Optimize Arm64 crc32c implementation in Postgresql - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Optimize Arm64 crc32c implementation in Postgresql
Date
Msg-id 87fu3891qd.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Optimize Arm64 crc32c implementation in Postgresql  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Optimize Arm64 crc32c implementation in Postgresql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 Tom> I also noticed that we'd been sloppy about making the file safe to
 Tom> compile for both frontend and backend, so I cleaned that up.

In a frontend, wouldn't it be more kosher to restore the previous SIGILL
handler rather than unconditionally reset it to SIG_DFL?

-- 
Andrew (irc:RhodiumToad)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimize Arm64 crc32c implementation in Postgresql
Next
From: Tom Lane
Date:
Subject: Re: Optimize Arm64 crc32c implementation in Postgresql