Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: "a(dot)kozhemyakin" <a(dot)kozhemyakin(at)postgrespro(dot)ru>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18610: llvm error: __aarch64_swp4_acq_rel which could not be resolved
Date: 2024-11-22 02:51:33
Message-ID: CA+hUKG+pDoAAJzdvXKCZCABPGhUzq7AgRZQ4Z+h8aMg=25f=ew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Nov 8, 2024 at 6:15 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Here's a patch for approach #3. This is low-urgency and a code freeze
> begins in a day or two, so I'm *not* proposing it for next week's
> release.

Hearing no objections, I pushed this.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message John Naylor 2024-11-22 04:39:15 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Previous Message Tom Lane 2024-11-22 00:11:09 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails