M. Zhou

One of the most significant performance bottleneck is `gemm`. The fully-connected layer (or say, linear layer, affine layer, dense layer, people use different names to refer exactly the same thing)...

One more thing to mention is that the licensing of deep neural networks is still an unclear area, unless the training dataset is fully open source. E.g., all training data...

Well. This ML-Policy draft is a result of a very lengthy discussion in debian-devel mailing list. So it has gone through some kind of review and reached somewhat a consensus....

This seems to be a randomly occurring problem. The second time I tried to trigger the build on arm64 has succeeded https://buildd.debian.org/status/logs.php?pkg=nqp&arch=arm64

BTW, the following is the default build flags for Debian (distribution-wide): ``` CFLAGS=-g -O2 -ffile-prefix-map=/home/lumin=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 FFLAGS=-g -O2 -ffile-prefix-map=/home/lumin=. -fstack-protector-strong -fstack-clash-protection -fcf-protection LDFLAGS=-Wl,-z,relro ```...

Ok, after fixing the test implementation (https://github.com/Reference-LAPACK/lapack/pull/964), the `ZDNRM2` test breaks again with Debian specific build flags. I think I should try to contribute a CI test with Debian build...

With the default flags in `make.inc`. The test passed. But with stack protections, you can reproduce the issue with (1) the following config, (2) Patch #964, and (3) the command...

looks good? @angsch

I have addressed the comments and force-pushed.

wrn for classification only.