From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: s_lock.h default definitions are rather confused |
Date: | 2015-01-10 23:06:41 |
Message-ID: | 20150110230641.GC27519@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-01-10 17:58:10 -0500, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > Given you got the error above, you used gcc. Have you used non-gcc
> > compiler on hppa recently? I seem to recall you mentioning that that
> > doesn't work sanely anymore? If so, perhaps we can just remove the !gcc
> > variant?
>
> It still compiles, modulo some old and uninteresting warnings, but linking
> the postgres executable fails with
>
> usr/ccs/bin/ld: Unsatisfied symbols:
> pg_compiler_barrier_impl (code)
> make[2]: *** [postgres] Error 1
Ick, that one is my failure.
> Curiously, there are no compiler warnings about "reference to undeclared
> function", which is odd because I see nothing that would declare that name
> as a function or macro for non-gcc HPPA.
Yea, that's odd.
> But in any case, the fallback logic for compiler barriers evidently
> still needs work.
Will fix (or well, try). It broke due to the atomics patch.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-01-10 23:34:16 | Re: s_lock.h default definitions are rather confused |
Previous Message | Tom Lane | 2015-01-10 22:58:10 | Re: s_lock.h default definitions are rather confused |