Re: Detection of hadware feature => please do not use signal
От | Tom Lane |
---|---|
Тема | Re: Detection of hadware feature => please do not use signal |
Дата | |
Msg-id | 1346552.1732549297@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Detection of hadware feature => please do not use signal (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Detection of hadware feature => please do not use signal
|
Список | pgsql-bugs |
I wrote: > I also confirmed that our existing code works on Fedora 30 armv7l > (also hard-float) with gcc 9.3.1. That's the only other ARM32 > image I have at hand :-( > So yeah, it would seem they broke it between 10.2.1 and 10.5.0. After discussion with the gcc folk (see bug report linked upthread) it emerges that there was indeed a change somewhere in that time frame. It used to be that if the platform defaults were "-march=A -mfpu=X" then writing "-march=B" on the command line would still leave you with "-mfpu=X", possibly a nonsensical combination. So now they ignore any build-time default, with the effect that writing just "-march=armv8-a+crc" selects soft float, which fails on platforms that require hard-float ABI. (I didn't ask whether this was the same change prompted by the other bug report you found, but perhaps it was.) Also, there's no +fp option for "-march=armv8-a" because the ARMv8 specs require chips to implement both or neither of FP and SIMD. So the idiomatic thing for us to write is not a separate -mfpu spec but "-march=armv8-a+crc+simd". I'll adjust my patch to do it like that and push later today. regards, tom lane
В списке pgsql-bugs по дате отправления: