Subject: Re: CVS commit: src/sbin/fsck
To: None <>
From: Simon Burge <>
List: source-changes
Date: 12/15/2006 12:41:22
Christos Zoulas wrote:

> Module Name:	src
> Committed By:	christos
> Date:		Wed Dec 13 16:08:26 UTC 2006
> Modified Files:
> 	src/sbin/fsck: fsck.c
> Log Message:
> Sprinkle volatile, instead of using the (void)&foo; which does not work on
> gcc 4.

Doesn't "volatile" cause the compiler to constantly load/store
those variables to the stack all the time instead of just keeping
them in registers if it can?  In other words, we now take a
performance hit just to shut up some gcc warnings?