| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Fix typo 586/686 in atomics/arch-x86.h |
| Date: | 2025-12-19 10:13:32 |
| Message-ID: | CAN4CZFPjoncMXo1ytihpOhPmzfKWS87Wo3Za_0tfGt_f4GYYKQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It does, but will this affect that? Does gcc change the CPU arch to 32bit era
> hardware when using -m32?
I did some quick testing with this, normally only __i386__ gets
defined for 32 bit builds (-march=native -m32 for example, but also
the default -march=x86-64 -m32). __i586__ and __i686__ are only there
if I pass the matching -march (i586/i686) flag to gcc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-12-19 10:18:21 | Re: Orphaned records in pg_replication_origin_status after subscription drop |
| Previous Message | Japin Li | 2025-12-19 10:07:24 | Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect |