| From: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: What exactly is our CRC algorithm? |
| Date: | 2014-12-30 07:06:11 |
| Message-ID: | 20141230070611.GA29360@toroid.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 2014-12-29 18:44:18 +0530, ams(at)2ndQuadrant(dot)com wrote:
>
> > > +#ifdef __GNUC__
> > > + __asm__ ("crc32b %[data], %[crc]\n" : [crc] "+r" (crc) : [data] "rm" (data));
> >
> > Have you checked which version of gcc introduced named references to
> > input/output parameters?
OK, here we go:
«As of GCC version 3.1, it is also possible to specify input and
output operands using symbolic names which can be referenced within
the assembler code.»
GCC 3.1 was released on May 15, 2002. So it should be quite safe to use
this feature.
-- Abhijit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2014-12-30 07:40:27 | Re: What exactly is our CRC algorithm? |
| Previous Message | Amit Kapila | 2014-12-30 07:02:41 | Re: Additional role attributes && superuser review |