Date: Wed, 31 Oct 2001 10:12:13 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Nate Williams <nate@yogotech.com> Cc: John Baldwin <jhb@FreeBSD.org>, chat@FreeBSD.org Subject: Re: time_t not to change size on x86 Message-ID: <3BE03EFD.8269DA73@mindspring.com> References: <XFMail.011030073149.jhb@FreeBSD.org> <3BDED411.DDEA0BD7@mindspring.com> <15326.55441.615206.243327@caddis.yogotech.com> <3BDFB74D.4EBD3145@mindspring.com> <15328.11194.623723.611472@caddis.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Nate Williams wrote: > > Actually, there are situations where you _must_ use volatile > > to prevent register optimization of variables. > > Only during OS type work, which most of the programmers never need to > worry about. Signal handlers. IPC via shared memory. Threads. ...lot of places where the optimizer wants to jam things in a register when you use loop control structures... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BE03EFD.8269DA73>