| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Pierre Ducroquet <pierre(dot)ducroquet(at)people-doc(dot)com> |
| Subject: | Re: JIT compiling with LLVM v9.1 |
| Date: | 2018-02-15 23:42:00 |
| Message-ID: | 353b583d-08a2-9097-2224-f2db093d44cf@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/15/2018 06:23 PM, Andres Freund wrote:
>> 2) When I build with --with-cassert I expect the assertions to be there,
>> both in the binaries and the bitcode. Is that just a bug or is there any
>> thought behind this?
>
> Not sure what you mean by that. NDEBUG and cassert are independent
> mechanisms, no?
Yeah, I think I just managed to confuse myself there.
The actual issue is that --with-llvm changes if NDEBUG is set or not,
which is quite surprising. I would not expect assertions to be disabled
in the fronted code just because I compiled PostgreSQL with llvm.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-02-16 01:07:08 | Re: [HACKERS] MERGE SQL Statement for PG11 |
| Previous Message | Alvaro Herrera | 2018-02-15 21:55:25 | Re: FOR EACH ROW triggers on partitioned tables |