Re: float4/float8/int64 passed by value with tsearch fixup - Mailing list pgsql-patches

From Alvaro Herrera
Subject Re: float4/float8/int64 passed by value with tsearch fixup
Date
Msg-id 20080418201924.GH572@alvh.no-ip.org
Whole thread Raw
In response to Re: float4/float8/int64 passed by value with tsearch fixup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: float4/float8/int64 passed by value with tsearchfixup
Re: float4/float8/int64 passed by value with tsearch fixup
List pgsql-patches
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).

Argh ... I would have certainly missed that.

> It'd be less ugly to convert to v1 calling convention.

Okay -- I'll change contrib/seg to v1 to greenify back the buildfarm.

> So I think we really do need to offer that compile-time option.
> Failing to do so will be tantamount to desupporting v0 functions
> altogether, which I don't think we're prepared to do.

I have asked the Cybertec guys for a patch.  Since it's basically a copy
of the float8 change, it should be easy to do.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: float4/float8/int64 passed by value with tsearch fixup
Next
From: Magnus Hagander
Date:
Subject: Re: Testing pg_terminate_backend()