From owner-freebsd-toolchain@freebsd.org  Sun Aug 14 23:34:34 2016
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00598BB96E4;
 Sun, 14 Aug 2016 23:34:34 +0000 (UTC) (envelope-from db@db.net)
Received: from diana.db.net (diana.db.net [66.113.102.10])
 by mx1.freebsd.org (Postfix) with ESMTP id E43441BDE;
 Sun, 14 Aug 2016 23:34:33 +0000 (UTC) (envelope-from db@db.net)
Received: from night.db.net (localhost [127.0.0.1])
 by diana.db.net (Postfix) with ESMTP id 9FBBA2AA4C8;
 Sun, 14 Aug 2016 17:33:48 -0600 (MDT)
Received: by night.db.net (Postfix, from userid 1000)
 id F2A591CDE4; Sun, 14 Aug 2016 19:34:30 -0400 (EDT)
Date: Sun, 14 Aug 2016 19:34:30 -0400
From: Diane Bruce <db@db.net>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: freebsd-ports@freebsd.org, freebsd-toolchain@freebsd.org
Subject: Re: Problems with out libgcc_s.so in base
Message-ID: <20160814233430.GA35872@night.db.net>
References: <20160814230351.GA10587@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160814230351.GA10587@troutmask.apl.washington.edu>
User-Agent: Mutt/1.6.1 (2016-04-27)
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 23:34:34 -0000

On Sun, Aug 14, 2016 at 04:03:51PM -0700, Steve Kargl wrote:
> 
> > The reason ports gcc now has this requirment on 4.6 or better is
> > fortran standard says we have to support quad floating point math.
> > e.g. /usr/local/lib/gccXX/libquadmath.so 
> 
> Diane,
> 
> Can you please stop with the dis-information?  No Fortran standard

I'm happy to be corrected. In this case it's immaterial if it is a
Fortran standard or not. It is what our present gcc from ports has given us.

...

> 
> FreeBSD-ports could avoid libquadmath issues by building gcc
> without it.  See --without-libquadmath or --without-quadmath (I
> don't remember the config option because it would be questionable
> to neuter one of gfortran's strength).

Correct. This blog entry I read some months ago outlines this
exact problem we are having and suggests the identical solution.

http://glennklockwood.blogspot.ca/2014/02/linux-perf-libquadmath-and-gfortrans.html

quadmath does have an impact on performance.


> 
> Freebsd-ports could also use a wrapper:
> % cat ~/bin/gfc7
> #! /bin/sh
> DIR=`id -P sgk | sed 's/\:/\ /g' | awk '{print $9}'`
> export DIR
> 
> LD_LIBRARY_PATH=$DIR/work/7/lib
> export LD_LIBRARY_PATH
> 
> LD_RUN_PATH=$DIR/work/7/lib
> export LD_RUN_PATH
> 
> $DIR/work/7/bin/gfortran -fno-backtrace $@

Yes. I have also suggested we use a wrapper to the ports guys.

- Diane
-- 
- db@FreeBSD.org db@db.net http://www.db.net/~db