On Sat, 13 Dec 2008, Warner Losh wrote:
Hi,
Is there (an easy) way to have the tinderbox build every other run without
VIMAGE_GLOBALS so that the most obvious error (global available, but not in
the container struct - or the other way around) can be warned about?
This actually points out why
From: Max Laier
Subject: Re: HEADS UP: vimage - virtualized global variables in the network
stack
Date: Sat, 13 Dec 2008 20:45:16 +0100
> On Saturday 13 December 2008 20:33:53 Bjoern A. Zeeb wrote:
> ...
> > This state of having the variables in parallel, global and in the
> >
On Sat, 13 Dec 2008, Max Laier wrote:
On Saturday 13 December 2008 20:33:53 Bjoern A. Zeeb wrote:
...
This state of having the variables in parallel, global and in the
container struct, will be maintained for another (short) time until
the entire virtualization framework is in. This is needed,
On Saturday 13 December 2008 20:33:53 Bjoern A. Zeeb wrote:
...
> This state of having the variables in parallel, global and in the
> container struct, will be maintained for another (short) time until
> the entire virtualization framework is in. This is needed, so that
> all three possible states
On Sat, 13 Dec 2008, Bjoern A. Zeeb wrote:
Hi,
Author: bz
Date: Sat Dec 13 19:13:03 2008
New Revision: 186048
URL: http://svn.freebsd.org/changeset/base/186048
Log:
Second round of putting global variables, which were virtualized
but formerly missed under VIMAGE_GLOBAL.
Put the extern decl
