Done and applied. > As long as we're cleaning things up, I would suggest that all the ports > that use gcc assembler be made to declare it uniformly, as > > __asm__ __volatile__ ( ... ); > > As I read the GCC manual, there's some risk of the asm sections getting > moved around in the program flow if they are not marked volatile. Also > we oughta be consistent about using the double-underscore keywords IMHO. > > regards, tom lane > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
- [HACKERS] s_lock.h cleanup Bruce Momjian
- Re: [HACKERS] s_lock.h cleanup Tom Lane
- [HACKERS] Re: [PATCHES] s_lock.h cleanup Bruce Momjian
- [HACKERS] Re: [PATCHES] s_lock.h cleanup Peter Eisentraut
- Re: [HACKERS] Re: [PATCHES] s_lock.h cleanup Bruce Momjian
- Re: [HACKERS] Re: [PATCHES] s_lock.h cleanup Tom Lane
- Re: [HACKERS] Re: [PATCHES] s_lock.h cle... Bruce Momjian
- Re: [HACKERS] Re: [PATCHES] s_lock.... Tom Lane
- Re: [HACKERS] Re: [PATCHES] s_l... Larry Rosenman
- Re: [HACKERS] Re: [PATCHES] s_l... Bruce Momjian
- Re: [HACKERS] Re: [PATCHES] s_lock.h cle... Bruce Momjian
- Re: [HACKERS] Re: [PATCHES] s_lock.... Ian Lance Taylor
- Re: [HACKERS] Re: [PATCHES] s_lock.h cleanup Tom Lane