Skip site navigation (1) Skip section navigation (2)

int8 & INT64_IS_BUSTED

From: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
To: Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: int8 & INT64_IS_BUSTED
Date: 2007-08-29 20:41:07
Message-ID: 46D5D9E3.8030505@phlo.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi

I'm confused about whether int8s work on a machine on which
INT64_IS_BUSTED. My reading of the code suggests that int8
will be available, but be, well, busted in such a machine.

For example, int8mul seems as if I'd just return the wrong
answer on such a machine.

Or are platforms with INT64_IS_BUSTED no longer supported,
and are all those #ifdefs only legacy code?

Please enlighten a poor linux+gcc user who can't remember
ever using a compiler without a "long long" datatype after
leaving TurboC under DOS.

greetings, Florian Pflug

Responses

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2007-08-29 21:05:54
Subject: text search function renaming
Previous:From: Alvaro HerreraDate: 2007-08-29 20:38:25
Subject: Re: [HACKERS] Contrib modules documentation online

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group