Re: [PATCH] Guard `CLOBBER_FREED_MEMORY` & `MEMORY_CONTEXT_CHECKING`

From: Jubilee Young <workingjubilee(at)gmail(dot)com>
To: Samuel Marks <samuelmarks(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Guard `CLOBBER_FREED_MEMORY` & `MEMORY_CONTEXT_CHECKING`
Date: 2024-08-24 04:55:43
Message-ID: CAPNHn3oU5FLKraPyX1p03+q3PznWTg-zLMgy7Y1xO-_p+fVBbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hmm, that seems like their problem not ours. It's not very clear
> to me why they'd want to force these flags from the compiler
> command line in the first place, but if they do they should be
> consistent with the more usual ways to set them.

There is no particular need to merge this patch for our sakes, as
the only reason it is this way was haste to build valgrind support.
Clang often finds some issue with the Postgres code style, so
I ignore its lint output, which is only regurgitated for errors anyway.
At least, in most build configurations. Happy to take any patches
for build stuff.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2024-08-24 07:26:02 Re: Optimising numeric division
Previous Message Alexander Lakhin 2024-08-24 04:00:00 Re: DELETE PENDING strikes back, via pg_ctl stop/start