Date: Mon, 07 May 2018 02:14:56 +0000 From: bugzilla-noreply@freebsd.org To: fortran@FreeBSD.org Subject: [Bug 228007] math/lapack: switch to flang Message-ID: <bug-228007-37611-HRa2B0WoEj@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 Johannes M Dieterich <jmd@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmd@freebsd.org --- Comment #7 from Johannes M Dieterich <jmd@freebsd.org> --- As the maintainer of devel/flang I agree with Steve here. flang is a) not y= et ready to replace gfortran (for the reasons Steve discussed) and b) only available for amd64. Personally, I hope this will change eventually and I h= ope we (as in FreeBSD) can help upstream by filing bug reports and vetting the compiler. I assume that you, Steve, filed these 100 internal compiler errors with fla= ng upstream so that we can track progress? Alternatively, could we get the Fortran test suite into the ports tree? I wouldn't mind having that myself to check flang updates. I see as a more viable alternative to get BLAS and LAPACK to Fortran-free implementations and am working on making blis and flame viable. Reference source-code implementations for BLAS/LAPACK are anyways a bad idea to use in production. That'll still leave a bunch of Fortran ports but at least it wo= uld be a start. --=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-HRa2B0WoEj>