volatile markings to silence compilers - Mailing list pgsql-hackers

From Bruce Momjian
Subject volatile markings to silence compilers
Date
Msg-id 201103170436.p2H4ax518362@momjian.us
Whole thread Raw
Responses Re: volatile markings to silence compilers
Re: volatile markings to silence compilers
List pgsql-hackers
Looking over the release notes, we have added a few 'volatile' storage
specifications to variables which are near longjump/TRY blocks to
silence compilers.  I am worried that these specifications don't clearly
identify their purpose.  Can we rename these to use a macro for
'volatile' that will make their purpose clearer and perhaps their
removal one day easier?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results
Next
From: Pavel Stehule
Date:
Subject: Re: patch: tabcomple for pset - format and linestyle