volatile markings to silence compilers

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: volatile markings to silence compilers
Date: 2011-03-17 04:36:59
Message-ID: 201103170436.p2H4ax518362@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2011-03-17 05:14:53 Re: patch: tabcomple for pset - format and linestyle
Previous Message Robert Haas 2011-03-17 02:40:37 Re: Re: [BUGS] BUG #5842: Memory leak in PL/Python when taking slices of results