From owner-freebsd-fortran@freebsd.org Mon May 7 04:07:19 2018 Return-Path: Delivered-To: freebsd-fortran@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57860FCE9E6 for ; Mon, 7 May 2018 04:07:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E085B6FD60 for ; Mon, 7 May 2018 04:07:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A4950FCE9E3; Mon, 7 May 2018 04:07:18 +0000 (UTC) Delivered-To: fortran@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FBD6FCE9E2 for ; Mon, 7 May 2018 04:07:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0CD06FD5A for ; Mon, 7 May 2018 04:07:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 072A1139D1 for ; Mon, 7 May 2018 04:07:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4747GMF008728 for ; Mon, 7 May 2018 04:07:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4747GGh008727 for fortran@FreeBSD.org; Mon, 7 May 2018 04:07:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fortran@FreeBSD.org Subject: [Bug 228007] math/lapack: switch to flang Date: Mon, 07 May 2018 04:07:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: sgk@troutmask.apl.washington.edu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fortran@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 May 2018 04:07:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228007 --- Comment #8 from sgk@troutmask.apl.washington.edu --- (In reply to Johannes M Dieterich from comment #7) > I assume that you, Steve, filed these 100 internal compiler > errors with flang upstream so that we can track progress? The flang developers have never responded to an initial bug report nor a post in flang-dev concerning a roadmap for an official release. Others have reported a few of the bugs that can be easily reproduced by trying to compile the gfortran testsuite. Preparing 100+ bug reports is beyond what I'm prepared to do. > Alternatively, could we get the Fortran test suite into > the ports tree? I wouldn't mind having that myself to > check flang updates. I am unaware of any stand alone testsuite. gfortran's testsuite tests for conformance where this includes programs that should compile and execute, and programs that should fail and the Fortran compiler must issue an error message. The former should compile and execute with flang. The latter will fail, but the testsuire isn't set up to test for flang error messages. > 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. Never heard of blis and flame. I'll check them out. One thing about Netlib BLAS and LAPACK is that the algorithms are designed by well-recognized numerical analysist. Yes, these routines are considered reference implementations, but the people behind them are well-respected. Robert pointed out that flang is almost F2003 complaint, which is commendable. Unfortunately, the current Fortran standard is Fortran 2008, and Fortran 2018 should be ratified within the next few months. gfortran, other than a bugs, is Fortran 2003 compliant, implements a significant portion of F2008, and has implemented some of the upcoming Fortran 2018 standard. I know because I either implemented the features or probably reviewed the patches that do. --=20 You are receiving this mail because: You are the assignee for the bug.=