| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Yuqi Gu <Yuqi(dot)Gu(at)arm(dot)com>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Optimize Arm64 crc32c implementation in Postgresql |
| Date: | 2018-05-03 03:25:43 |
| Message-ID: | 28977.1525317943@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> "Thomas" == Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> + uint64 data = 42;
> Isn't there a hidden assumption about endianness there?
Yeah, I was wondering about that too, but does anyone actually run
ARMs big-endian?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Cui | 2018-05-03 03:51:54 | Re: GSoC 2018: thrift encoding format |
| Previous Message | Andrew Gierth | 2018-05-03 03:20:57 | Re: Optimize Arm64 crc32c implementation in Postgresql |