From owner-freebsd-ports@FreeBSD.ORG Thu Apr 14 07:52:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 442E5106566C for ; Thu, 14 Apr 2011 07:52:14 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id F0B708FC12 for ; Thu, 14 Apr 2011 07:52:13 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1QAHLY-0003pX-Ub>; Thu, 14 Apr 2011 09:52:13 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1QAHLY-00076P-S5>; Thu, 14 Apr 2011 09:52:12 +0200 Message-ID: <4DA6A7B1.2090805@zedat.fu-berlin.de> Date: Thu, 14 Apr 2011 09:52:17 +0200 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: bf1783@gmail.com References: <4DA68D86.3000102@mail.zedat.fu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: "O. Hartmann" , brooks@freebsd.org, "b. f." , freebsd-ports@freebsd.org Subject: Re: Does USE_GCC= 4.5+ also set C++ and Fortran to g++45/46 and gfortran45/46? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2011 07:52:14 -0000 On 04/14/11 08:32, b. f. wrote: > On 4/14/11, O. Hartmann wrote: >> On 04/13/11 20:59, b. f. wrote: > >> I looked into ports/Mk/bsd.gcc.mk and found that only gcc45 is set in >> case of using USE_FORTRAN, not gcc46. It would be nice also having gcc46 >> set, since we try to optimise for AVX in the new Intel Sandy-Bridge CPUs >> and gcc46 is supoorting new facilities like that. > > I think that the gcc maintainer will probably switch the default > Fortran compiler to gcc46 after gcc46 has been tested a bit longer, > and some of the remaining bugs fixed. You could of course switch the > default on your own machines. AVX support requires more than just a > new compiler and the proper hardware: at the moment, FreeBSD doesn't > support AVX, although some outside developers expressed an interest in > adding support for it: > > http://lists.freebsd.org/pipermail/freebsd-arch/2011-March/011167.html > > but this will probably take some time. > > b. Regarding the gcc46: I hope so. I read about the interest for AVX support in FreeBSd. But we try to optimize some code for numerical simulations to adopt SSE and, f available, AVX support by coding assembler or with the GNU compiler __attribute__ intrinsics. But this is also a bit of science-fiction for AVX for now. We had hope for clang, but clang lacks in many aspects we desperately need - like OpenMP support. Oliver