Re: Detection of hadware feature => please do not use signal

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Bastien Roucariès <rouca(at)debian(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Detection of hadware feature => please do not use signal
Date: 2024-11-24 00:08:55
Message-ID: 885805.1732406935@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Sun, Nov 24, 2024 at 11:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> cc1: error: '-mfloat-abi=hard': selected processor lacks an FPU

> Interesting. Happens also on Linux starting with GCC 11, apparently.
> Here's one with some clues:
> https://github.com/checkpoint-restore/criu/issues/1653#issuecomment-986034428

Oh, very interesting! Maybe we need to try -march=armv8-a+crc+fp
(or some spelling like that) if -march=armv8-a+crc doesn't work?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-11-24 01:42:00 Re: BUG #18722: Processing arrays with plpgsql raises errors
Previous Message Thomas Munro 2024-11-23 23:50:09 Re: Detection of hadware feature => please do not use signal