public inbox for [email protected]  

help / color / mirror / Atom feed

From: Greg Burd <[email protected]>
To: Tom Lane <[email protected]>
To: Michael Paquier <[email protected]>
To: Alexander Lakhin <[email protected]>
Cc: pgsql-hackers <[email protected]>
Cc: Thomas Munro <[email protected]>
Subject: Re: pgcrypto/des tests fail on riscv64 due to clang's code generation anomaly
Date: Mon, 16 Mar 2026 08:13:55 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>


On Sun, Mar 15, 2026, at 9:40 PM, Tom Lane wrote:
> Michael Paquier <[email protected]> writes:
>> On Sun, Mar 15, 2026 at 02:00:00PM +0200, Alexander Lakhin wrote:
>>> adding -march=rv64gcv to CFLAGS makes clang generate different (wrong?)
>>> code for crypt-des.c. Namely, having reproduced the diff locally, with
>>> this debugging addition:
>>> when the code compiled with CC=clang-20 CPPFLAGS="-march=rv64gcv".
>
>> Thanks for the detailed investigation.  I was puzzled by it myself for
>> a couple of hours, and did not see something else than a broken
>> compiler here..
>
> Seems like this might be worth a bug report to the clang people.

Thanks Alexander for digging and a solid report of the issue, and Michael for spending some time on this, and Tom for chiming in as well.  I agree this looks like a compiler issue.  I know that Thomas (added/CC'ed) you've posted bugs against clang before, any thoughts on this one?

>
> 			regards, tom lane

best.

-greg

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: pgcrypto/des tests fail on riscv64 due to clang's code generation anomaly
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox