Horton

Re: Fix typo 586/686 in atomics/arch-x86.h

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Zsolt Parragi <zsolt.parragi@percona.com>
Cc: John Naylor <johncnaylorls@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Jakub Wartak <jakub.wartak@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-12-20T21:31:13Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove support for 8 byte tear free read/write on 32-bit

Zsolt Parragi <zsolt.parragi@percona.com> writes:
> It seems this is dependent on the linux distribution. I assumed gcc
> uses the same march on all modern linux distributions, but that
> doesn't seem to be the case.

It may be changing with time, too.  Same experiment on Red Hat distros:

gcc 8.5.0 on RHEL8:
$ gcc -Q --help=target | grep march
  -march=                               x86-64
$ gcc -m32 -Q --help=target | grep march
  -march=                               x86-64

gcc 11.5.0 on RHEL9:
$ gcc  -Q --help=target | grep march
  -march=                               x86-64-v2
  Known valid arguments for -march= option:
$ gcc -m32 -Q --help=target | grep march
  -march=                               x86-64
  Known valid arguments for -march= option:

gcc 14.3.1 on Fedora 41:
$ gcc -Q --help=target | grep march
  -march=                               x86-64
  Known valid arguments for -march= option:
$ gcc -m32 -Q --help=target | grep march
  -march=                               i686
  Known valid arguments for -march= option:

			regards, tom lane