Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 06 May 2018 21:33:28 +0000
From:      bugzilla-noreply@freebsd.org
To:        fortran@FreeBSD.org
Subject:   [Bug 228007] math/lapack: switch to flang
Message-ID:  <bug-228007-37611-OxZTeMXRIt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-228007-37611@https.bugs.freebsd.org/bugzilla/>
References:  <bug-228007-37611@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228007

robert.ayrapetyan@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #193117|text/x-log                  |text/plain
          mime type|                            |

--- Comment #3 from robert.ayrapetyan@gmail.com ---
Created attachment 193117
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D193117&action=
=3Dedit
poudriere log for a patched port

Hi, thanks for a prompt reply!

Globally defined: DEFAULT_VERSIONS+=3D    fortran=3Dflang
will break all ports using gfortran-specific FFLAGS
(e.g.-ffixed-line-length-none) and not using flang's replacements (e.g.
-Mextend).
In case of a math/lapack there are also incompatibilities with e.g. ETIME
function:=20
gfortran requires it to be INTERNAL (default make.inc), flang - EXTERNAL
(requires make.inc patch) etc.
A suggested patch makes math/lapack to build using flang on amd64 only and
passes all tests after that (see attached poudriere log).
Other platforms should be unaffected and will continue to use gfortran.
> devel/flang-clang has been marked broken
hm, thanks, I've missed that somehow... I've just commited a patch for it (=
see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222254#c12).
gfortran's FreeBSD issue is really annoying and affects virtually all
scientific packages (e.g. Python's Keras, or recently added math/mlpack).
With FreeBSD's movement from gcc to clang, flang is the only right choice i=
n a
long-term perspective.
To avoid even more issues and incompatibilities in the future I'm encouragi=
ng
FreeBSD's ports maintainers to make this switch ASAP.

Thanks!

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228007-37611-OxZTeMXRIt>