Bug#818341: gnutls28: FTBFS on amd64: assumes build machine has all CPU extensions

Andreas Metzler ametzler at bebt.de
Thu Mar 17 18:38:01 UTC 2016


Control: forwarded -1 http://lists.gnutls.org/pipermail/gnutls-devel/2016-March/007943.html

On 2016-03-16 Simon McVittie <smcv at debian.org> wrote:
[...]
> It seems to me as though it would be more useful for test coverage if
> the meaning of GNUTLS_CPUID_OVERRIDE was changed from "assume the CPU
> has exactly these extensions" to "use only these extensions, even if
> the CPU has others". Pseudocode now:

>     if (GNUTLS_CPUID_OVERRIDE)
>         extensions = parse (GNUTLS_CPUID_OVERRIDE);
>     else
>         extensions = cpuid ();

> Pseudocode that I think would be more useful:

>     extensions = cpuid ();

>     if (GNUTLS_CPUID_OVERRIDE)
>         extensions &= parse (GNUTLS_CPUID_OVERRIDE);

That is actually how it is supposed to worked, however the logic was
only correctly implemented for VIA extensions.

> Longer-term, it would also be great if the tests (at least those that do not
> require much environment setup) could be packaged as "installed tests"
> similar to those in glib2.0, so that they can be re-run on systems that
> differ from the buildd.

I will think about that, thanks for the pointer.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the Pkg-gnutls-maint mailing list