Date: Sun, 06 May 2018 22:33:06 +0000 From: bugzilla-noreply@freebsd.org To: fortran@FreeBSD.org Subject: [Bug 228007] math/lapack: switch to flang Message-ID: <bug-228007-37611-t0Tk1QTTtj@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 sgk@troutmask.apl.washington.edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sgk@troutmask.apl.washingto | |n.edu --- Comment #4 from sgk@troutmask.apl.washington.edu --- (In reply to robert.ayrapetyan from comment #3) > 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#c= 12). > 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 > in a long-term perspective. To avoid even more issues and incompatibiliti= es > in the future I'm encouraging FreeBSD's ports maintainers to make this > switch ASAP. As a long time user of FreeBSD (since it was called 386BSD+patchkit) and a long time contributor to both FreeBSD and gfortran, can you elaborate on gfortran's FreeBSD issue. Switching to Flang without actually testing its performance, conformance to standards, and quality is somewhat a questionable move. Last time I tried compiling gfortran's testsuite with Flang, it found somewhere around 100 internal compiler errors. --=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-t0Tk1QTTtj>