Re: Add support for __attribute__((returns_nonnull))

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Tristan Partin <tristan(at)neon(dot)tech>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add support for __attribute__((returns_nonnull))
Date: 2024-01-01 03:29:19
Message-ID: CANWCAZbtRnK0BzwvUCD1OY_bXyYct_-t7XLo5RcY5K2TY3FJdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 28, 2023 at 1:20 AM Tristan Partin <tristan(at)neon(dot)tech> wrote:
> I recently wound up in a situation where I was checking for NULL return
> values of a function that couldn't ever return NULL because the
> inability to allocate memory was always elog(ERROR)ed (aborted).

It sounds like you have a ready example to test, so what happens with the patch?

As for whether any code generation changed, I'd start by checking if
anything in a non-debug binary changed at all.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2024-01-01 03:35:27 Re: Commitfest manager January 2024
Previous Message vignesh C 2024-01-01 03:19:59 Re: Commitfest 2024-01 starting in 3 days!