Why is (void)&variable; construct used?

[Matthew Dillon]

:
:On Tue, Apr 26, 2005 at 10:58:34AM -0700, Max Okumoto wrote:
:> With the new gcc do we still need the following construct?
:
:It's a way to force the symbols as used. Remove them.
:
:Joerg

    No, it's a way to force the variable declarations to NOT be placed
    in registers, so changes to the variables effect the parent of a
    vfork (if they are in registers then they don't effect the parent).
    GCC complains about that situation for vfork, setjmp, and longjmp
    usage.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>