| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | hlinnaka(at)iki(dot)fi |
| Cc: | Max Filippov <jcmvbkbc(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Peter Seiderer <ps(dot)report(at)gmx(dot)net> |
| Subject: | Re: configure can't detect proper pthread flags |
| Date: | 2015-07-08 13:38:13 |
| Message-ID: | 20320.1436362693@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> I suggest that we revert that work-around for that GCC bug, and stop
> testing the pthread flags as soon as we find one that works.
OK ...
> Then we can
> also remove the test for whether the compiler produces any warnings.
Don't see how that follows?
> AFAICS, after that our ax_thread.m4 file is not materially different
> from the upstream autoconf-archive version. Let's just replace our
> ax_pthread.m4 file with the latest upstream version.
It definitely *would* be nice to get back in sync with the upstream
version of that file. But I'm unconvinced about the warnings angle.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-07-08 13:40:03 | Re: Freeze avoidance of very large table. |
| Previous Message | Simon Riggs | 2015-07-08 13:31:04 | Re: Freeze avoidance of very large table. |