Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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>

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


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group