On 6/23/16 10:10 AM, Wei Liu wrote:
> Originally hvm_fep was guarded by NDEBUG, which means it was only
> available to debug builds.
>
> However there is value to have it for non-debug builds as well. User can
> use that to run tests in setup that replicates production setup.
"Users can use it to
On 23/06/16 16:26, Wei Liu wrote:
> On Thu, Jun 23, 2016 at 04:24:40PM +0100, Andrew Cooper wrote:
>> On 23/06/16 16:10, Wei Liu wrote:
>>> Originally hvm_fep was guarded by NDEBUG, which means it was only
>>> available to debug builds.
>>>
>>> However there is value to have it for non-debug builds
On Thu, Jun 23, 2016 at 04:24:40PM +0100, Andrew Cooper wrote:
> On 23/06/16 16:10, Wei Liu wrote:
> > Originally hvm_fep was guarded by NDEBUG, which means it was only
> > available to debug builds.
> >
> > However there is value to have it for non-debug builds as well. User can
> > use that to ru
On 23/06/16 16:10, Wei Liu wrote:
> Originally hvm_fep was guarded by NDEBUG, which means it was only
> available to debug builds.
>
> However there is value to have it for non-debug builds as well. User can
> use that to run tests in setup that replicates production setup.
That is odd phrasing.
>>> On 23.06.16 at 17:10, wrote:
> Originally hvm_fep was guarded by NDEBUG, which means it was only
> available to debug builds.
>
> However there is value to have it for non-debug builds as well. User can
> use that to run tests in setup that replicates production setup.
>
> Make it clear with
Originally hvm_fep was guarded by NDEBUG, which means it was only
available to debug builds.
However there is value to have it for non-debug builds as well. User can
use that to run tests in setup that replicates production setup.
Make it clear with a sync_console style warning that this option c
