Re: float4/float8/int64 passed by value with tsearchfixup
| От | Tom Lane |
|---|---|
| Тема | Re: float4/float8/int64 passed by value with tsearchfixup |
| Дата | |
| Msg-id | 24749.1208556084@sss.pgh.pa.us обсуждение |
| Ответ на | Re: float4/float8/int64 passed by value with tsearchfixup (Gregory Stark <stark@enterprisedb.com>) |
| Ответы |
Re: float4/float8/int64 passed by value with tsearchfixup
Re: float4/float8/int64 passed by value with tsearchfixup |
| Список | pgsql-patches |
Gregory Stark <stark@enterprisedb.com> writes:
>> Tom Lane wrote:
>>> Specifically, I think what you missed is that on some platforms C
>>> functions pass or return float values differently from similar-sized
>>> integer or pointer values (typically, the float values get passed in
>>> floating-point registers).
> Hum. That's a valid concern for some platforms, Sparc I think?
> But I'm skeptical that it would hit such a wide swathe of the build
> farm.
I was wondering about that too, once it became obvious that (almost?)
everything was failing not just some platforms. However, this
afternoon's CVS HEAD *does* pass the seg regression test for me on HPPA,
and I presume it passed on whatever Alvaro is using (btw, what was
that?). So there's definitely a platform dependency involved and not
just you-missed-a-pointer-someplace.
regards, tom lane
В списке pgsql-patches по дате отправления: