From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Henry <rrh.henry@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: postgres has no spinlock support on riscv rv64imafdc
Date: Fri, 18 Oct 2019 09:00:23 +0200
Message-ID: <27501.1571382023@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEYr_8nnwxQji0pQJYqFx7=gSM8x7jFJi16O-bLuVYvqvkjsLg@mail.gmail.com>
References: <CAEYr_8nnwxQji0pQJYqFx7=gSM8x7jFJi16O-bLuVYvqvkjsLg@mail.gmail.com>
Robert Henry <rrh.henry@gmail.com> writes:
> Building Postgres from scratch on the riscv board, no fancy cross
> compilation, I get:
> PostgreSQL does not have native spinlock support on this platform. To
> continue the compilation, rerun configure using --disable-spinlocks.
> However, performance will be poor. Please report this to
> pgsql-bugs@lists.postgresql.org.
The last we heard about RISC-V was this thread:
https://www.postgresql.org/message-id/flat/20161119230312.GA8656%40redhat.com
If things seem to work well now with --disable-spinlocks, maybe you
could test the patch suggested in that thread. TBH, though, my preference
would be for some assembly code rather than relying on GCC builtins
as Richard's patch did.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, rrh.henry@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: postgres has no spinlock support on riscv rv64imafdc
In-Reply-To: <27501.1571382023@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox