mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leonard Lausen <>
Subject Update on non-compliant releases on and how to obtain a compliant build
Date Fri, 19 Jun 2020 00:40:51 GMT
As per the consensus in [1], I requested INFRA to delete the MXNet convenience
binaries on [2].

Zach previously offered to organize a third-party Maven distribution. However,
based on recently updated version 0.4 of the draft Apache Downstream
Distribution Branding Policy published in June 2020, the ASF does not allow the
use of the MXNet for referring to a non-compliant distribution, taking the
position that this would constitute a trademark infringement. Thus such third-
party distributions are required to happen under a name not trademarked by the
ASF. [3]

On the question of building compliant CPU convenience binaries that can be
distributed under the name MXNet, ASF now agrees that the previous stance of
"" is GPL and can't be distributed is incorrect based on the GCC
Runtime Library Exception [4]. itself still has a runtime
dependency on pure GPL, which can't be redistributed by ASF
projects, but (unlike has a stable ABI and we can
ask users to install on their systems to use the MXNet
convenience binary.

Instead of relying on the GNU Fortran compiler and introducing the dependency, I tried using the Flang Fortran compiler [5]. In
principle, it works well. But there are still a couple of bugs in OpenBLAS
and/or Flang which mean that one needs to build OpenBLAS with -O1 optimization
instead of -O2 to pass the test-suite. [6] This may be fixed in the next
OpenBLAS release. One reason is that Flang performs more aggressive optimization
and vectorization, meaning that once these bugs are fixed we may also find speed
improvements by switching to Flang toolchain.

Best regards


View raw message