Re: Fix typo 586/686 in atomics/arch-x86.h - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fix typo 586/686 in atomics/arch-x86.h
Date
Msg-id 6822.1766266273@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fix typo 586/686 in atomics/arch-x86.h  (Zsolt Parragi <zsolt.parragi@percona.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Implement waiting for wal lsn replay: reloaded
Next
From: Tom Lane
Date:
Subject: Re: Inline non-SQL SRFs using SupportRequestSimplify