From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 06:35:14 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86475B3F for ; Tue, 9 Jul 2013 06:35:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0191B10 for ; Tue, 9 Jul 2013 06:35:11 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r696ZBaT033275 for ; Mon, 8 Jul 2013 23:35:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r696ZBMm033274 for freebsd-fortran@freebsd.org; Mon, 8 Jul 2013 23:35:11 -0700 (PDT) (envelope-from sgk) Date: Mon, 8 Jul 2013 23:35:11 -0700 From: Steve Kargl To: freebsd-fortran@freebsd.org Subject: Fortran list? Message-ID: <20130709063510.GA33261@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 06:35:14 -0000 Wow, a Fortran list. I thought I was one of the few who still uses Fortran. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 16:49:09 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A4D515E6 for ; Tue, 9 Jul 2013 16:49:09 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog108.obsmtp.com (eu1sys200aog108.obsmtp.com [207.126.144.125]) by mx1.freebsd.org (Postfix) with ESMTP id 097F01CA2 for ; Tue, 9 Jul 2013 16:49:08 +0000 (UTC) Received: from mail-ee0-f46.google.com ([74.125.83.46]) (using TLSv1) by eu1sys200aob108.postini.com ([207.126.147.11]) with SMTP ID DSNKUdw+/qQpk+CzXMWme+DnmlSHI4C/sdXT@postini.com; Tue, 09 Jul 2013 16:49:09 UTC Received: by mail-ee0-f46.google.com with SMTP id d41so3812385eek.33 for ; Tue, 09 Jul 2013 09:49:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:x-gm-message-state; bh=T2iTY+EYlzStmCqStRfz6590w1AzpTxT02tJTu5H3Tw=; b=o+e3dy1Ax7tlIWberKHsV0861bE2siHDO9M4LB+EIhXjaHpwYJeOPYvPwL9m0kI5m1 KlRIplBu5qB3YTDoCnMD00ft55b3nLGm61L3aa+waO6NggW1RQSCZeGIp6Zk9MmaVJdZ YY5WeiQDrTF+mcoO3G6xB1Af2iEgPkmSYz/HvpN44Soc9oOa4tcP64zH9pwf1s3KAg2X G4i5+FuLQq0rDdt9ts4pSWsFc3q9N4c1Ym4gAy83c/NbvKPE+qA3TIURVsgHFOO1DQBn L18miUx1dnij0Dlc7jq2L4tOFHK0aClIAJXJaZh8YFX+0rLzZVTmHtLJ0O/GFzf7LiR/ q7wQ== X-Received: by 10.14.110.194 with SMTP id u42mr31375064eeg.128.1373388168896; Tue, 09 Jul 2013 09:42:48 -0700 (PDT) X-Received: by 10.14.110.194 with SMTP id u42mr31375054eeg.128.1373388168819; Tue, 09 Jul 2013 09:42:48 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id e44sm52272579eeh.11.2013.07.09.09.42.47 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 09:42:47 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r69GgjI1071179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 9 Jul 2013 17:42:45 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r69GgjXF071178 for freebsd-fortran@freebsd.org; Tue, 9 Jul 2013 17:42:45 +0100 (BST) (envelope-from mexas) Date: Tue, 9 Jul 2013 17:42:45 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> To: freebsd-fortran@freebsd.org Subject: why fortran mailing list? X-Gm-Message-State: ALoCoQnTlYdNQeFtzHvFyi7NKB6kEwWUBcKAg+7nJh/ZOZPPj+Lgy10pb1a2Nt8BZI1eHPn2flOIFOLEJcvoJ9VOog8vmn+drD7myyo42lhwUJVxDQREr6EOvLuuBbNE3FyvKW1iCJG2lfBH4dFyD2HNCEBFZ/XaMiSKD7yk9Ffxu8lplhTux0M= X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 16:49:09 -0000 Steve, you beat me to post the first message... I suggested this list in: http://lists.freebsd.org/pipermail/freebsd-doc/2013-June/022145.html In addition to the reasons in that post, here's one more: this list might be a better maintainer than ports@ for several fortran related ports. Anton From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 19:28:54 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AF5384A7 for ; Tue, 9 Jul 2013 19:28:54 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog104.obsmtp.com (eu1sys200aog104.obsmtp.com [207.126.144.117]) by mx1.freebsd.org (Postfix) with ESMTP id 142541762 for ; Tue, 9 Jul 2013 19:28:50 +0000 (UTC) Received: from mail-ee0-f42.google.com ([74.125.83.42]) (using TLSv1) by eu1sys200aob104.postini.com ([207.126.147.11]) with SMTP ID DSNKUdxkbP+3vqNxuP1BmSr2FPZ/qoA6paOW@postini.com; Tue, 09 Jul 2013 19:28:54 UTC Received: by mail-ee0-f42.google.com with SMTP id c4so4004776eek.29 for ; Tue, 09 Jul 2013 12:28:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:x-gm-message-state; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=hT5xkDy0zpqq3xYIHa1jUjROabvJXvF6Ubry4lpZeL7rsZycmvlyTwKN7vt2Bvk3Ft X4dFfcxQ5XdktcTh0MB+WP9SwKeiJDoSkcI7iiCCAlrAw+3A2SmkvPN/qSCKBKQuQVC3 h7hJEY+/J2vp0qqIsfzrMYGiYfh2BzZMUNTzT0UM9XJbHtkpb9RievJZAWLD4A8Om2D4 2/7dvDF186LCSjyXEkjOeorxTM6lMUCGMwBkMtUC4L/fNmY6MajgrV/414YmHLi/y6Mr dMe89T4Aax5sju+2gc10tGNsSbaMU61WYWXFW11zKnKkndQae6Ge2MG9pdlHHeiDzZAj Ru8w== X-Received: by 10.15.32.67 with SMTP id z43mr32538565eeu.24.1373397745632; Tue, 09 Jul 2013 12:22:25 -0700 (PDT) X-Received: by 10.15.32.67 with SMTP id z43mr32538563eeu.24.1373397745569; Tue, 09 Jul 2013 12:22:25 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id o5sm53481666eef.5.2013.07.09.12.22.23 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Jul 2013 12:22:24 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r69JMMqq083214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 9 Jul 2013 20:22:22 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r69JMMEt083213 for fortran@freebsd.org; Tue, 9 Jul 2013 20:22:22 +0100 (BST) (envelope-from mexas) Date: Tue, 9 Jul 2013 20:22:22 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307091922.r69JMMEt083213@mech-cluster241.men.bris.ac.uk> To: fortran@freebsd.org Subject: checking alias fortran@freebsd.org X-Gm-Message-State: ALoCoQmbctRBT4qw2iKxYsrVNh5ce/wMGlcmEsUbPKY3FJYPPHTNKSjx51Xmffpyo8t3/8BcS/7DS5rlPe3vzpxNdgfwo2B7pDzkQ0nMwLyWaTfB+ga9k80b4wAOLwgN8+mnD+jxSzpVw7jna4Mwl1YhrUlOAeioIA== X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 19:28:54 -0000 From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 23:18:12 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D8DF985F for ; Tue, 9 Jul 2013 23:18:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id BF6AC1321 for ; Tue, 9 Jul 2013 23:18:12 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r69NI9YH092968; Tue, 9 Jul 2013 16:18:09 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r69NI83C092967; Tue, 9 Jul 2013 16:18:08 -0700 (PDT) (envelope-from sgk) Date: Tue, 9 Jul 2013 16:18:08 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: why fortran mailing list? Message-ID: <20130709231808.GA92444@troutmask.apl.washington.edu> References: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 23:18:12 -0000 On Tue, Jul 09, 2013 at 05:42:45PM +0100, Anton Shterenlikht wrote: > Steve, you beat me to post the first message... Well, I scan the email archives every few days, and I was surprised to see a Fortran specific list. > I suggested this list in: > http://lists.freebsd.org/pipermail/freebsd-doc/2013-June/022145.html > > In addition to the reasons in that post, > here's one more: this list might > be a better maintainer than ports@ for > several fortran related ports. > The few ports that I use, which need Fortran, seem to just work. This is probably due to the backwards compatibility of Fortran 2008 with F2003, F95, F90, and F77. OpenMPI is the only Fortran code that I routinely build outside of the ports. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 23:24:33 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E5682AE8 for ; Tue, 9 Jul 2013 23:24:33 +0000 (UTC) (envelope-from chris@uminac.com) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) by mx1.freebsd.org (Postfix) with ESMTP id BBE971370 for ; Tue, 9 Jul 2013 23:24:33 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id f4so13375798iea.25 for ; Tue, 09 Jul 2013 16:24:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:x-gm-message-state; bh=frLaTEDuXDQKb6WLDWkFYpRbqTo0kysUvthTICJwQZQ=; b=eH12GCL0oHyojFvfr9FV+gIzxhy8YJ0bfdBzrzrb7VszylhQeM10M/N6KiIN3UpsN8 TBHuACw1t9s+JLfwyNBEnFw1jb0rDb+CSJvdAud65NI3qf/1Dtt4MmQ1F0JPZGZDT4wt rlGzQbbuQnvg4BjSDyDIdg2SrlVGSxxGoyeZk9/YN5LeacOiTvWDp1yjFu3uPfscmtH1 Tv1f0cNKjC+8ITEuvlzafSajgSA/PC3/7qMt8BJIdVPyiD2dcLgFI8DcZuhTW47uEyYH W93IgQIuDQDTWJcoL7U3b8j/JuoyZHY/bQFsvn5BlQEOKlZlJdB5XY8FA4bybBy3IzZT Wv+g== X-Received: by 10.50.73.106 with SMTP id k10mr10973155igv.31.1373412272962; Tue, 09 Jul 2013 16:24:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.19.179 with HTTP; Tue, 9 Jul 2013 16:24:12 -0700 (PDT) X-Originating-IP: [216.93.242.164] In-Reply-To: <20130709231808.GA92444@troutmask.apl.washington.edu> References: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> <20130709231808.GA92444@troutmask.apl.washington.edu> From: "Christopher J. Umina" Date: Tue, 9 Jul 2013 19:24:12 -0400 Message-ID: Subject: Re: why fortran mailing list? To: Steve Kargl Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnNjPVv2p48HQ9lA+/oKRs+FE+gA2/+T5BEAKi0a28Rf6MQy9w9Crvhbzvqi0Cq1WRRw1ug Cc: mexas@bristol.ac.uk, freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 23:24:34 -0000 Fortran is pretty much a standard in the scientific world and I for one have been quite upset about the fact that I'm constantly forced away from FreeBSD for such things. Needless to say I was quite surprised that a list was created specifically for Fortran discussion, but I'm also very excited to see the level of interest in the community. On Tue, Jul 9, 2013 at 7:18 PM, Steve Kargl wrote: > On Tue, Jul 09, 2013 at 05:42:45PM +0100, Anton Shterenlikht wrote: >> Steve, you beat me to post the first message... > > Well, I scan the email archives every few days, and I > was surprised to see a Fortran specific list. > >> I suggested this list in: >> http://lists.freebsd.org/pipermail/freebsd-doc/2013-June/022145.html >> >> In addition to the reasons in that post, >> here's one more: this list might >> be a better maintainer than ports@ for >> several fortran related ports. >> > > The few ports that I use, which need Fortran, seem to just > work. This is probably due to the backwards compatibility > of Fortran 2008 with F2003, F95, F90, and F77. OpenMPI is > the only Fortran code that I routinely build outside of the > ports. > > -- > Steve > _______________________________________________ > freebsd-fortran@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fortran > To unsubscribe, send any mail to "freebsd-fortran-unsubscribe@freebsd.org" -- Christopher J. Umina chris@uminac.com 781 354 0535 From owner-freebsd-fortran@FreeBSD.ORG Tue Jul 9 23:31:53 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 01B16B59 for ; Tue, 9 Jul 2013 23:31:52 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id D883F13A2 for ; Tue, 9 Jul 2013 23:31:52 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r69NVn5l093645; Tue, 9 Jul 2013 16:31:49 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r69NVnp0093643; Tue, 9 Jul 2013 16:31:49 -0700 (PDT) (envelope-from sgk) Date: Tue, 9 Jul 2013 16:31:49 -0700 From: Steve Kargl To: "Christopher J. Umina" Subject: Re: why fortran mailing list? Message-ID: <20130709233149.GA93320@troutmask.apl.washington.edu> References: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> <20130709231808.GA92444@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mexas@bristol.ac.uk, freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2013 23:31:53 -0000 On Tue, Jul 09, 2013 at 07:24:12PM -0400, Christopher J. Umina wrote: > Fortran is pretty much a standard in the scientific world and I for > one have been quite upset about the fact that I'm constantly forced > away from FreeBSD for such things. Needless to say I was quite > surprised that a list was created specifically for Fortran discussion, > but I'm also very excited to see the level of interest in the > community. > Please, don't top-post, it looses context. In fact, I've deleted all of the previous context. :-) Not sure why you're forced away from FreeBSD because of Fortran. gfortran has been a part of GCC since 2005. Although the first year or two of gfortran's life saw a large number of bugsi and patches, since gcc 4.4,x ori 4.5.x, she's been a very good compiler. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 00:27:27 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 13EF8A94 for ; Wed, 10 Jul 2013 00:27:27 +0000 (UTC) (envelope-from estrabd@gmail.com) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id CFC1D18B9 for ; Wed, 10 Jul 2013 00:27:26 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id s1so3393505qcw.1 for ; Tue, 09 Jul 2013 17:27:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tuFw9uq0wiDP6LoLwOnQ7bYgTNmGXdZSJtg3tS7qJ9Y=; b=Z2skxoWJzksRv488s4jtP9Sk0rPGn7ixeVZ6s8a0v6P8u9Gc3QD7efdEqj3AL3+Dte k2eTA3ndIvTKINti4/NlFFS1pF5nG4cQwbUMz2LGJTvUzwHc55TE7cu71Z/++uUmJurB JskonLlQSHhnKcabegVCAC6R9jJpLIsdQUFlaV83E5Q2TbbUikMiT0rE2betJKrl1V69 m8UcM6ZS6tdKzWuuOkpNg5757J94K3XwwsKOI5E2kqYqNJyaD01e9PazsVEjz82TQ+Tn DyV8DgDbr8v2jDmIIDJgF0nBfsdksroZj9oQEmjqRqA8Qp5EGwqcWwOp28LqUXIBUaTz BV6w== MIME-Version: 1.0 X-Received: by 10.224.21.6 with SMTP id h6mr11313848qab.14.1373416046428; Tue, 09 Jul 2013 17:27:26 -0700 (PDT) Received: by 10.229.201.138 with HTTP; Tue, 9 Jul 2013 17:27:26 -0700 (PDT) In-Reply-To: <20130709233149.GA93320@troutmask.apl.washington.edu> References: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> <20130709231808.GA92444@troutmask.apl.washington.edu> <20130709233149.GA93320@troutmask.apl.washington.edu> Date: Tue, 9 Jul 2013 19:27:26 -0500 Message-ID: Subject: Re: why fortran mailing list? From: "B. Estrade" To: freebsd-fortran@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 00:27:27 -0000 On Tuesday, 9 July 2013, Steve Kargl wrote: > On Tue, Jul 09, 2013 at 07:24:12PM -0400, Christopher J. Umina wrote: > > Fortran is pretty much a standard in the scientific world and I for > > one have been quite upset about the fact that I'm constantly forced > > away from FreeBSD for such things. Needless to say I was quite > > surprised that a list was created specifically for Fortran discussion, > > but I'm also very excited to see the level of interest in the > > community. > > > > Please, don't top-post, it looses context. In fact, I've > deleted all of the previous context. :-) > > Not sure why you're forced away from FreeBSD because of > Fortran. gfortran has been a part of GCC since 2005. > Although the first year or two of gfortran's life saw a > large number of bugsi and patches, since gcc 4.4,x ori > 4.5.x, she's been a very good compiler. > > gfortran had not been part of base gcc for some time, and now that gcc is out altogether you lose even basic OpenMP support to clang. OpenMP on FreeBSD is the primary reason for my interest here. Brett -- > Steve > _______________________________________________ > freebsd-fortran@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fortran > To unsubscribe, send any mail to "freebsd-fortran-unsubscribe@freebsd.org > " > From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 00:50:47 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 07F0CF6 for ; Wed, 10 Jul 2013 00:50:47 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id C75331986 for ; Wed, 10 Jul 2013 00:50:46 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6A0okjX055599; Tue, 9 Jul 2013 17:50:46 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6A0ok7q055598; Tue, 9 Jul 2013 17:50:46 -0700 (PDT) (envelope-from sgk) Date: Tue, 9 Jul 2013 17:50:46 -0700 From: Steve Kargl To: "B. Estrade" Subject: Re: why fortran mailing list? Message-ID: <20130710005046.GA55507@troutmask.apl.washington.edu> References: <201307091642.r69GgjXF071178@mech-cluster241.men.bris.ac.uk> <20130709231808.GA92444@troutmask.apl.washington.edu> <20130709233149.GA93320@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 00:50:47 -0000 On Tue, Jul 09, 2013 at 07:27:26PM -0500, B. Estrade wrote: > On Tuesday, 9 July 2013, Steve Kargl wrote: > > > On Tue, Jul 09, 2013 at 07:24:12PM -0400, Christopher J. Umina wrote: > > > Fortran is pretty much a standard in the scientific world and I for > > > one have been quite upset about the fact that I'm constantly forced > > > away from FreeBSD for such things. Needless to say I was quite > > > surprised that a list was created specifically for Fortran discussion, > > > but I'm also very excited to see the level of interest in the > > > community. > > > > > > > Please, don't top-post, it looses context. In fact, I've > > deleted all of the previous context. :-) > > > > Not sure why you're forced away from FreeBSD because of > > Fortran. gfortran has been a part of GCC since 2005. > > Although the first year or two of gfortran's life saw a > > large number of bugsi and patches, since gcc 4.4,x ori > > 4.5.x, she's been a very good compiler. > > > > > gfortran had not been part of base gcc for some time, Are you talking about the version of gcc bundled in the base system? Yeah, Fortran was removed when GCC 4.something sources were imported into the FreeBSD source tree. OTOH, gfortran has been apart of GNU GCC since April of 2005. There is no reason why one could not install gfortran/gcc from source. With the speed of development, one in fact would want to occasional update GCC to get the improvements introduced into gfortran. > and now that gcc is out altogether you lose even basic > OpenMP support to clang. Huh, what are you talking about here? gfortran/gcc has had OpenMP for a long time. OpenMP support was added to gcc 4.2 on 2006-02-14. OpenMP version 3 was introduced into gcc 4.4 and version 3 was upgraded to 3.1 in gcc 4.7. It not even clear if clang has openmp support, yet. Not to llvm does not have a Fortran compiler! From the llvm home page: 3. dragonegg -- integrates the LLVM optimizers and code generator with the GCC parsers. This allows LLVM to compile Ada, Fortran, and other languages supported by the GCC compiler frontends, and access to C features not supported by Clang (such as OpenMP). > OpenMP on FreeBSD is the primary reason for my interest here. OK. So, then you'll be using gfortran? -- Steve From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 08:02:39 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D0EEA8A7 for ; Wed, 10 Jul 2013 08:02:39 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog124.obsmtp.com (eu1sys200aog124.obsmtp.com [207.126.144.157]) by mx1.freebsd.org (Postfix) with ESMTP id 33AA81A9C for ; Wed, 10 Jul 2013 08:02:38 +0000 (UTC) Received: from mail-ee0-f53.google.com ([74.125.83.53]) (using TLSv1) by eu1sys200aob124.postini.com ([207.126.147.11]) with SMTP ID DSNKUd0VHYY5/OH/eebPXI6Ds8E6gI0enBl2@postini.com; Wed, 10 Jul 2013 08:02:39 UTC Received: by mail-ee0-f53.google.com with SMTP id c41so4624188eek.26 for ; Wed, 10 Jul 2013 01:02:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=3tjcKIOJ9oG+NDfXfBiRsSnE+oAUHWrm4GeW8UwnnqQ=; b=KffjUEEm7CutwfG79ch4iIckuoIUpfzQddF+mMWbkkyI365pvxxN75wH14b/mmEcA2 Lyl+8Iv7F031mUd+2AROhNH4SKKpa+zeJnZV7BZ9mLrE08dR2HVn8OQJ/4vrxzlUrkq4 1zJyKd+w5P1M1C/0psVqtvfR9B4D64bfXpWhjof5NSTxPaqxJrO1IIJrJQKqCFT9XhwV Iy+PQWbYnwXiBI6vuj9jeK/eXESmyERnKLB2NBCCE1MXTPbLm3ym1273gHlEbfXHqHNB L/ri9Q5YXsL3K87vsZ4AXPXLHTl41/sdasZasq0uKc0caU8c8eeheR2myRt7lnyRhAD2 LH5w== X-Received: by 10.15.99.2 with SMTP id bk2mr34803213eeb.76.1373443357827; Wed, 10 Jul 2013 01:02:37 -0700 (PDT) X-Received: by 10.15.99.2 with SMTP id bk2mr34803205eeb.76.1373443357764; Wed, 10 Jul 2013 01:02:37 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id y1sm57928672eew.3.2013.07.10.01.02.35 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 01:02:36 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6A82Yd9098987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Jul 2013 09:02:34 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6A82X99098986; Wed, 10 Jul 2013 09:02:33 +0100 (BST) (envelope-from mexas) Date: Wed, 10 Jul 2013 09:02:33 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307100802.r6A82X99098986@mech-cluster241.men.bris.ac.uk> To: chris@uminac.com, sgk@troutmask.apl.washington.edu Subject: Re: why fortran mailing list? In-Reply-To: X-Gm-Message-State: ALoCoQnzyBQquJr20EZDPFtmOam1pnLd3xlPOoLGSk+8yojvNxvUqpDXg8Al7QTZNfHtulLTxYXnDcKnAY0CBFJG1aszqW5mRqgIkNMsLArqtmdwtjXetGQfpqvvu+8VO41tiuJfiAhBqtX16fpgyX65PWeS6L4itLSXPLOZ4Yl1aH/SE5DpbDc= Cc: mexas@bristol.ac.uk, freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 08:02:39 -0000 From chris@uminac.com Wed Jul 10 00:33:36 2013 Fortran is pretty much a standard in the scientific world and I for one have been quite upset about the fact that I'm constantly forced away from FreeBSD for such things. Needless to say I was quite surprised that a list was created specifically for Fortran discussion, but I'm also very excited to see the level of interest in the community. You are the community. There is no secret ingredient. It's just you and me and others. If we want better fortran support in FreeBSD, it's up to us to make it happen. I also hate to be forced to do much of my fortran work on linux. Anton From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 08:05:59 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 18BC08EA for ; Wed, 10 Jul 2013 08:05:59 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog112.obsmtp.com (eu1sys200aog112.obsmtp.com [207.126.144.133]) by mx1.freebsd.org (Postfix) with ESMTP id 6FA131ABC for ; Wed, 10 Jul 2013 08:05:57 +0000 (UTC) Received: from mail-ee0-f42.google.com ([74.125.83.42]) (using TLSv1) by eu1sys200aob112.postini.com ([207.126.147.11]) with SMTP ID DSNKUd0V5Xm3dPqP4FOq8dRH+wuftxt10T2e@postini.com; Wed, 10 Jul 2013 08:05:58 UTC Received: by mail-ee0-f42.google.com with SMTP id c4so4724612eek.1 for ; Wed, 10 Jul 2013 01:05:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=nVS4JVywxBNYNEdnas5E9O8S99PtBxhmxoycQbwQBF8=; b=cnFb5VdtXwXs/J9HkU1ouQ7PRNdpeITflIEoZIhvEj0AiFS9bF6DCtLA03FTy2nRv/ 8FSK1P0+1KuDWK4qb2Mwk5i/O0qJuc+qHdkTnJ1f3C1Zffc38XeXhZZSLa2h5Q2LVEf3 AQC99sMKeO7x0r18xOmwtrdaKqGSO9Wib16vIEJ+sszj7IKcUQIHQSPgkx6Ov05wasSv KwzzHD+yjPGuR74lHGYXX0SLwdb1f/9fTUp7oqTPBXuoKb2uUbNzV3Cgdd1vASgAg0Tg edTchmkkcjm/ZCiUZMSE9PMuh8UMT4366F6d7hYczF0NZ6iPoFIb+zd6oHuQi2PsgSTS kpKw== X-Received: by 10.14.100.2 with SMTP id y2mr34918778eef.75.1373443196860; Wed, 10 Jul 2013 00:59:56 -0700 (PDT) X-Received: by 10.14.100.2 with SMTP id y2mr34918769eef.75.1373443196748; Wed, 10 Jul 2013 00:59:56 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id n42sm57785968eeh.15.2013.07.10.00.59.54 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 00:59:55 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6A7xqwq098966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Jul 2013 08:59:52 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6A7xqsK098965; Wed, 10 Jul 2013 08:59:52 +0100 (BST) (envelope-from mexas) Date: Wed, 10 Jul 2013 08:59:52 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu Subject: Re: why fortran mailing list? In-Reply-To: <20130709231808.GA92444@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQlMSv6FIRd9pJltE6vUb43Y38Flf87L2/62GNNF+1HQg2fXzXU2J5zCP43kSohcJlH+DkH3ZKj1ofZGqM5tXLOjqlamlmhvUkqxLbz2ERz7ur1WhMUpKzh/2mVnD0ZtjVFhQ3cBfBO79B1XwP6Oy0yXyq35n5UeNBTVakleXfjUIs4Lrdo= Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 08:05:59 -0000 From sgk@troutmask.apl.washington.edu Wed Jul 10 00:33:34 2013 The few ports that I use, which need Fortran, seem to just work. That's not my experience. For example french/aster, a major FE suite, fails on both amd64 and ia64: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176326 As far as I know it fails on places other than fortran, but it is largely "a fortran port". OpenMPI is the only Fortran code that I routinely build outside of the ports. Please elaborate. I don't know much about the differences between OpenMPI and mpich. The latter seems to work: # pkg info -xr mpi mpich2-1.3.2.p1_1,5: scotch-5.1.12.b.e astk-serveur-1.11.0 blocksolve95-3.0_10 ParMetis-4.0_1 # Anton From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 08:21:00 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4B9D9C34 for ; Wed, 10 Jul 2013 08:21:00 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog114.obsmtp.com (eu1sys200aog114.obsmtp.com [207.126.144.137]) by mx1.freebsd.org (Postfix) with ESMTP id B47991B41 for ; Wed, 10 Jul 2013 08:20:58 +0000 (UTC) Received: from mail-ea0-f179.google.com ([209.85.215.179]) (using TLSv1) by eu1sys200aob114.postini.com ([207.126.147.11]) with SMTP ID DSNKUd0ZYtinoB0tzbUt1fzXJQaTQkwqh0vg@postini.com; Wed, 10 Jul 2013 08:20:58 UTC Received: by mail-ea0-f179.google.com with SMTP id b15so4687190eae.38 for ; Wed, 10 Jul 2013 01:20:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=R2xau3MrSdBoqsgvwJPs+Y44o//5i39urB/IZrcv61w=; b=gXw46VIIl9/ffrW3n9t1v/GeJ5gCU4728fEI9NFz1nKkDuK/RTyZuCMh5Jy1IF/dLn dLDiR++KUnQ8afiMYFDP4Jc5dxdhn3J6MR5oYupAJ9wVVvR49nzcppL+4ytV00AVe7FF ijrfSUtHkO8tXPin3L9YXMwW/Uci2eMH8GdiwOgR1tASoilRMZ96iG3XZoE64uTvJo6b 7sYJOA//xqzIZOv1ZU1V6xe4dw4UIwZ1vNWXe1ggTCi8d49FzXdC+Ti9XfBoWZK/JOIY 1ENMNAs+fAUGQbiJh4QZm1YP7A3DJnuyQiHRPVPKI1zVnaPIZEVZ86A8lT5s7zcSZFq3 LYFw== X-Received: by 10.14.95.69 with SMTP id o45mr34898199eef.48.1373444450797; Wed, 10 Jul 2013 01:20:50 -0700 (PDT) X-Received: by 10.14.95.69 with SMTP id o45mr34898189eef.48.1373444450710; Wed, 10 Jul 2013 01:20:50 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id b3sm57963943eev.10.2013.07.10.01.20.48 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 01:20:49 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6A8KlYj099329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Jul 2013 09:20:47 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6A8KkNm099328; Wed, 10 Jul 2013 09:20:46 +0100 (BST) (envelope-from mexas) Date: Wed, 10 Jul 2013 09:20:46 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307100820.r6A8KkNm099328@mech-cluster241.men.bris.ac.uk> To: chris@uminac.com, sgk@troutmask.apl.washington.edu Subject: Re: why fortran mailing list? In-Reply-To: <20130709233149.GA93320@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQkRjv7VrdQjSBlwivYvEswd8MZATtReugFcFVB2nxsRQSmjRi+AQc/u/yDBpZuWEt4jZAcSDH9+2AVaYMBDBsZ0h1WS83aNlt4vcb1XLjfqLQ9rZCwEup6I002QePO1FDLYGCdG2817XBr/ByoKJ3IX7yXX1VRFovwo1TZJFskXqpEiUjc= Cc: mexas@bristol.ac.uk, freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 08:21:00 -0000 From sgk@troutmask.apl.washington.edu Wed Jul 10 00:33:37 2013 On Tue, Jul 09, 2013 at 07:24:12PM -0400, Christopher J. Umina wrote: > Fortran is pretty much a standard in the scientific world and I for > one have been quite upset about the fact that I'm constantly forced > away from FreeBSD for such things. Needless to say I was quite > surprised that a list was created specifically for Fortran discussion, > but I'm also very excited to see the level of interest in the > community. > Please, don't top-post, it looses context. In fact, I've deleted all of the previous context. :-) Not sure why you're forced away from FreeBSD because of Fortran. gfortran has been a part of GCC since 2005. Although the first year or two of gfortran's life saw a large number of bugsi and patches, since gcc 4.4,x ori 4.5.x, she's been a very good compiler. Right now I need coarrays, so I have to use other compilers on linux. But a compiler alone is not enough. I need a complete tightly integrated fortran environment, with libraries and applications. Many libs/apps available on linux are not in ports yet. One example is Trilinos, http://trilinos.sandia.gov/packages/fortrilinos/. I think bf@ has been working on a port. But there are more, I just can't think of any at the moment. Then there are things like legacy code. For example, I myself maintain math/slatec, which is 1980-1990 fortran 77 library with over 1400 subroutines. I found this library useful at some point. But the code is old and completely unmaintained, perhaps there are better newer alternatives. Should it stay in ports for now? Anton From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 08:47:17 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5818F3E3 for ; Wed, 10 Jul 2013 08:47:17 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from mx1a.lautre.net (eyra.lautre.net [80.67.160.71]) by mx1.freebsd.org (Postfix) with ESMTP id 1FE6B1C92 for ; Wed, 10 Jul 2013 08:47:16 +0000 (UTC) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: thierry@pompo.net) by mx1a.lautre.net (Postfix) with ESMTPSA id AF19840B16 for ; Wed, 10 Jul 2013 10:47:14 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id D0A6342D853A; Wed, 10 Jul 2013 10:47:13 +0200 (CEST) Date: Wed, 10 Jul 2013 10:47:13 +0200 From: Thierry Thomas To: freebsd-fortran@freebsd.org Subject: Re: why fortran mailing list? Message-ID: <20130710084713.GA73590@graf.pompo.net> References: <20130709231808.GA92444@troutmask.apl.washington.edu> <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 9.1-STABLE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 08:47:17 -0000 Le mer 10 jul 13 à 9:59:52 +0200, Anton Shterenlikht écrivait : > That's not my experience. > For example french/aster, a major FE suite, > fails on both amd64 and ia64: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176326 > > As far as I know it fails on places other than fortran, > but it is largely "a fortran port". Yes Code_Aster has problems, but PR ports/176328 is caused by another problem located in metis-edf (a patch has been provided, and we are waiting for the maintainer to commit it). Other problems are caused by a mismatch between legacy code and recent compilers. E.g.: http://www.code-aster.org/forum2/viewtopic.php?id=16215 http://www.code-aster.org/forum2/viewtopic.php?id=16194 but they are not specific to FreeBSD, and the newer releases of Code_Aster (unstable ATM) have fixed them. Regards, -- Th. Thomas. From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 09:08:51 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 009D87B2 for ; Wed, 10 Jul 2013 09:08:50 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog112.obsmtp.com (eu1sys200aog112.obsmtp.com [207.126.144.133]) by mx1.freebsd.org (Postfix) with ESMTP id 46FC21D70 for ; Wed, 10 Jul 2013 09:08:49 +0000 (UTC) Received: from mail-ea0-f177.google.com ([209.85.215.177]) (using TLSv1) by eu1sys200aob112.postini.com ([207.126.147.11]) with SMTP ID DSNKUd0koR6S8jW9JKUSh6TeHe020dS7fRnj@postini.com; Wed, 10 Jul 2013 09:08:50 UTC Received: by mail-ea0-f177.google.com with SMTP id j14so4777648eak.22 for ; Wed, 10 Jul 2013 02:08:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:in-reply-to :x-gm-message-state; bh=qubg2ryDKSJOJaKLmFQNF9pTPYib+TSppJ/+ZT5WBeU=; b=acGj8OvDVSF/zkUOHeabtvdZW8SvUUfw56GsVRVsdKVH/X1mWu0VDB/uoOMSG4IL1M zOQa2vVbrcoV1VJbZKRSHhvgwbvcFV7oS7LC+L1f5l3lf9JjQxmMWQAtI/SACl1rw6Fe QOroKDaxEWv03MwaDmgJlE5lXnaYtjarZpf7vFHkLMJKjT0e3OyhYnIUUcfhJS7oU/mP ihM5NfgYTUuQ4tm7fij5NoYRbCiqWrpq34iFUa8ttiLIo+H//PBmgrdbV6VFfLX+RqSI 1vgiIU7PKNcjSqyxT4aAtY2ewmef/TLQSJEv+CJO5J5eSfo4MGBYWQPOphG1rNQeM7/N udww== X-Received: by 10.14.7.2 with SMTP id 2mr34989718eeo.145.1373447329009; Wed, 10 Jul 2013 02:08:49 -0700 (PDT) X-Received: by 10.14.7.2 with SMTP id 2mr34989711eeo.145.1373447328937; Wed, 10 Jul 2013 02:08:48 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id ci50sm58248638eeb.12.2013.07.10.02.08.46 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 02:08:47 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6A98j3I001343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Jul 2013 10:08:45 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6A98jOM001342; Wed, 10 Jul 2013 10:08:45 +0100 (BST) (envelope-from mexas) Date: Wed, 10 Jul 2013 10:08:45 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> To: freebsd-fortran@freebsd.org, thierry@FreeBSD.org Subject: Re: why fortran mailing list? In-Reply-To: <20130710084713.GA73590@graf.pompo.net> X-Gm-Message-State: ALoCoQkA34VbKCSvt9dLAgaRxbdzxiIaS0vpriPQPM8Ph4yJ9QTJkLQsqRCuOBp9bXu0k9uuj1PT1/jXelKhb5pZg8yUXscUNiPmKxM3QiItaf3lSbMsqY+Sa2wauddwToH9hhCtTEqvinqF9varOX59VomdGgrEsKq9PCnz6g9lqEJPXdY5j58= X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 09:08:51 -0000 Date: Wed, 10 Jul 2013 10:47:13 +0200 From: Thierry Thomas To: freebsd-fortran@freebsd.org Subject: Re: why fortran mailing list? > That's not my experience. > For example french/aster, a major FE suite, > fails on both amd64 and ia64: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176326 > > As far as I know it fails on places other than fortran, > but it is largely "a fortran port". Yes Code_Aster has problems, but PR ports/176328 is caused by another problem located in metis-edf (a patch has been provided, and we are Regarding this patch, is it ok to just put it unde files, as: # ls files/ medis-patch-Lib_Makefile.txt patch-Lib::proto.h patch-Test::Makefile patch-CONFIG::configure patch-Lib_Makefile patch-onmetis patch-CONFIG_onmetis.in patch-Programs::Makefile # How does the ports framework know that medis-patch-Lib_Makefile.txt must be applied *after* patch-Lib_Makefile, i.e. on top of it? Anton P.S. Please ignore my reply to ports/176328. I understand now what to do. From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 13:38:25 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 19C073F9 for ; Wed, 10 Jul 2013 13:38:25 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from mx1a.lautre.net (eyra.lautre.net [80.67.160.71]) by mx1.freebsd.org (Postfix) with ESMTP id D67A61DD7 for ; Wed, 10 Jul 2013 13:38:24 +0000 (UTC) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: thierry@pompo.net) by mx1a.lautre.net (Postfix) with ESMTPSA id 44D5240A5B for ; Wed, 10 Jul 2013 15:38:18 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id A833142D28ED; Wed, 10 Jul 2013 15:38:17 +0200 (CEST) Date: Wed, 10 Jul 2013 15:38:17 +0200 From: Thierry Thomas To: freebsd-fortran@freebsd.org Subject: Re: why fortran mailing list? Message-ID: <20130710133817.GB41178@graf.pompo.net> Mail-Followup-To: freebsd-fortran@freebsd.org References: <20130710084713.GA73590@graf.pompo.net> <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 9.1-STABLE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 13:38:25 -0000 Le mer 10 jul 13 à 11:08:45 +0200, Anton Shterenlikht écrivait : > Regarding this patch, is it ok to just put it > unde files, as: > > # ls files/ > medis-patch-Lib_Makefile.txt patch-Lib::proto.h patch-Test::Makefile > patch-CONFIG::configure patch-Lib_Makefile patch-onmetis > patch-CONFIG_onmetis.in patch-Programs::Makefile > # > > How does the ports framework know that > medis-patch-Lib_Makefile.txt must be applied > *after* patch-Lib_Makefile, i.e. on top of it? Actually, it has to be renamed as patch-*. And patches are applied sorted by their name. > P.S. Please ignore my reply to ports/176328. > I understand now what to do. Great! -- Th. Thomas. From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 14:18:10 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF27F79B for ; Wed, 10 Jul 2013 14:18:10 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog119.obsmtp.com (eu1sys200aog119.obsmtp.com [207.126.144.147]) by mx1.freebsd.org (Postfix) with ESMTP id 4298510BA for ; Wed, 10 Jul 2013 14:18:09 +0000 (UTC) Received: from mail-ea0-f169.google.com ([209.85.215.169]) (using TLSv1) by eu1sys200aob119.postini.com ([207.126.147.11]) with SMTP ID DSNKUd1tIdAL4zbMOfiGfRHEgfmg7qKf24tl@postini.com; Wed, 10 Jul 2013 14:18:10 UTC Received: by mail-ea0-f169.google.com with SMTP id h15so5073187eak.28 for ; Wed, 10 Jul 2013 07:18:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to :x-gm-message-state; bh=K3NWJThkCb/xqQ1QuvBo5ulNg8ILj9eck6kYMRjv2FY=; b=IyTwKwmdh+NENjLqW4RBKpGO0ZelFPXruxM5sDtoDc0ByN4OykQD/GDorD3DefB+1N 1dfAphPMihaG9V/kNvKAUkrmtGaxM3/q+uvQa8gBQPnLoDsW/3Jkn5xCx1CweEluLD47 q+Jhr8Igfp7uf5YB3sDukDSPA82rQ+NvuskdjN7PbKzhbGEgXr/Zd43vi3ctmvJvmkm2 qTDtbQkOCgaaSTNtlZmzSn2ypHvSaXQRNzdlEwblaZG4TCXFjttj4dESK3hyLyacCGim MP42jb7esuA1Sj1TBpkMu+JsShQZDEMNo5jA+z8NXiTtR4UxE6xW0AAjFBjzEjDxxcV/ JJyg== X-Received: by 10.15.83.69 with SMTP id b45mr36100758eez.150.1373465888909; Wed, 10 Jul 2013 07:18:08 -0700 (PDT) X-Received: by 10.15.83.69 with SMTP id b45mr36100741eez.150.1373465888705; Wed, 10 Jul 2013 07:18:08 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id bj46sm60246328eeb.13.2013.07.10.07.18.06 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 07:18:07 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6AEI5Uv073778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 10 Jul 2013 15:18:05 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6AEI50f073777; Wed, 10 Jul 2013 15:18:05 +0100 (BST) (envelope-from mexas) Date: Wed, 10 Jul 2013 15:18:05 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307101418.r6AEI50f073777@mech-cluster241.men.bris.ac.uk> To: bf@freebsd.org, maho@freebsd.org, thierry@FreeBSD.org Subject: cad/aster + cad/calculix: math/metis-edf confilicts with math/metis4 X-Gm-Message-State: ALoCoQkeGpzZSOw71+SphKaaa5lgAC48YdMtQ3CcMpyWm11hD2iV0FX4CKWdk29cr/8b+X9d2KhzzY4UasYBo1nKGzql58eUK4fIelIo3EUJEkkJBZsznTutBrE3rNEAAPyqKBH3hnwp1EkjuQ1ntUxfwXMmjXmMew== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 14:18:10 -0000 I'd like to have a workstation for UG projects with several engineering packages available. I've now got code_aster to install. However, I hit this conflict installing calculix: ===> metis-4.0.3_1 conflicts with installed package(s): metis-edf-4.1.2_3 How best to resolve this? The easiest solution would be to make them install in different places. Or am I missing something? Thanks Anton From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 16:20:15 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9C40A89D; Wed, 10 Jul 2013 16:20:15 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from mx1a.lautre.net (eyra.lautre.net [80.67.160.71]) by mx1.freebsd.org (Postfix) with ESMTP id 644171B86; Wed, 10 Jul 2013 16:20:15 +0000 (UTC) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: thierry@pompo.net) by mx1a.lautre.net (Postfix) with ESMTPSA id B546D40A45; Wed, 10 Jul 2013 18:20:13 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id EFC7B42D7F81; Wed, 10 Jul 2013 18:20:12 +0200 (CEST) Date: Wed, 10 Jul 2013 18:20:12 +0200 From: Thierry Thomas To: mexas@bristol.ac.uk Subject: Re: cad/aster + cad/calculix: math/metis-edf confilicts with math/metis4 Message-ID: <20130710162012.GA87694@graf.pompo.net> References: <201307101418.r6AEI50f073777@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201307101418.r6AEI50f073777@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 9.1-STABLE i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: maho@freebsd.org, fortran@freebsd.org, bf@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 16:20:15 -0000 Hello, Le mer 10 jul 13 à 16:18:05 +0200, Anton Shterenlikht écrivait : > I'd like to have a workstation for UG projects > with several engineering packages available. > I've now got code_aster to install. > However, I hit this conflict installing calculix: > > ===> metis-4.0.3_1 conflicts with installed package(s): > metis-edf-4.1.2_3 > > How best to resolve this? > > The easiest solution would be to make > them install in different places. > Or am I missing something? Yes, this is a possibility. Another one could be to see if calculix could depend on metis-edf: this one is just a fork of metis, with small modifications. Regards, -- Th. Thomas. From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 17:07:45 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 418B1129 for ; Wed, 10 Jul 2013 17:07:45 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 264E21E34 for ; Wed, 10 Jul 2013 17:07:45 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6AH7BQg059568; Wed, 10 Jul 2013 10:07:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6AH7BGB059567; Wed, 10 Jul 2013 10:07:11 -0700 (PDT) (envelope-from sgk) Date: Wed, 10 Jul 2013 10:07:11 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: why fortran mailing list? Message-ID: <20130710170711.GA59476@troutmask.apl.washington.edu> References: <20130709231808.GA92444@troutmask.apl.washington.edu> <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307100759.r6A7xqsK098965@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 17:07:45 -0000 On Wed, Jul 10, 2013 at 08:59:52AM +0100, Anton Shterenlikht wrote: > From sgk@troutmask.apl.washington.edu Wed Jul 10 00:33:34 2013 > >> OpenMPI is >> the only Fortran code that I routinely build outside of the >> ports. > > Please elaborate. > I don't know much about the differences between OpenMPI > and mpich. The latter seems to work: > > # pkg info -xr mpi > mpich2-1.3.2.p1_1,5: > scotch-5.1.12.b.e > astk-serveur-1.11.0 > blocksolve95-3.0_10 > ParMetis-4.0_1 I've used both mpich2 and OpenMPI on i386 and amd64 systems. In the testing I've done with my applications, OpenMPI simply out performed mpich2. This was a while ago, so things may have changed. OpenMPI just works. The one issue I had with OpenMPI was resolved within a day. Note, I do not use ports/net/openmpi. I download the latest version from the OpenMPI, unpack it, run configure and install. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 17:16:40 2013 Return-Path: Delivered-To: freebsd-fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 861A760E for ; Wed, 10 Jul 2013 17:16:40 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4F1F51EB9 for ; Wed, 10 Jul 2013 17:16:40 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6AHGbSo059631; Wed, 10 Jul 2013 10:16:37 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6AHGa0H059630; Wed, 10 Jul 2013 10:16:36 -0700 (PDT) (envelope-from sgk) Date: Wed, 10 Jul 2013 10:16:36 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: why fortran mailing list? Message-ID: <20130710171636.GB59476@troutmask.apl.washington.edu> References: <20130709233149.GA93320@troutmask.apl.washington.edu> <201307100820.r6A8KkNm099328@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307100820.r6A8KkNm099328@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 17:16:40 -0000 On Wed, Jul 10, 2013 at 09:20:46AM +0100, Anton Shterenlikht wrote: > From sgk@troutmask.apl.washington.edu Wed Jul 10 00:33:37 2013 > > On Tue, Jul 09, 2013 at 07:24:12PM -0400, Christopher J. Umina wrote: > > Fortran is pretty much a standard in the scientific world and I for > > one have been quite upset about the fact that I'm constantly forced > > away from FreeBSD for such things. Needless to say I was quite > > surprised that a list was created specifically for Fortran discussion, > > but I'm also very excited to see the level of interest in the > > community. > > > > Please, don't top-post, it looses context. In fact, I've > deleted all of the previous context. :-) > > Not sure why you're forced away from FreeBSD because of > Fortran. gfortran has been a part of GCC since 2005. > Although the first year or two of gfortran's life saw a > large number of bugsi and patches, since gcc 4.4,x ori > 4.5.x, she's been a very good compiler. > > Right now I need coarrays, so I have to use other compilers > on linux. gfortran has single-image co-array support. As you know, Tobias has slowly been working on co-arrays, and IIRC the only missing functionality is runtime support. He could use some help writing that support, so now is your chance to contribute. > But a compiler alone is not enough. > I need a complete tightly integrated fortran > environment, with libraries and applications. Then, you're on your own. The FreeBSD ports collection cannot provide the tight integration that you desire. > Many libs/apps available on linux are not > in ports yet. One example is Trilinos, > http://trilinos.sandia.gov/packages/fortrilinos/. > I think bf@ has been working on a port. > But there are more, I just can't think of > any at the moment. Why wait for a port to appear in the Port Collection. Grab the code you need and build it. > Then there are things like legacy code. > For example, I myself maintain math/slatec, > which is 1980-1990 fortran 77 library > with over 1400 subroutines. > I found this library useful at some point. > But the code is old and completely unmaintained, > perhaps there are better newer alternatives. > Should it stay in ports for now? Of course. Why remove a functioning port? The beauty of old (standard conforming) Fortran coder is that it will compile with modern Fortran compilers. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 23:15:55 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0C80394F for ; Wed, 10 Jul 2013 23:15:55 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog114.obsmtp.com (eu1sys200aog114.obsmtp.com [207.126.144.137]) by mx1.freebsd.org (Postfix) with ESMTP id 621BE10EA for ; Wed, 10 Jul 2013 23:15:53 +0000 (UTC) Received: from mail-ea0-f180.google.com ([209.85.215.180]) (using TLSv1) by eu1sys200aob114.postini.com ([207.126.147.11]) with SMTP ID DSNKUd3rFBmdz2dGRZv08hLxTzuZFuZ5cn/c@postini.com; Wed, 10 Jul 2013 23:15:54 UTC Received: by mail-ea0-f180.google.com with SMTP id k10so5382726eaj.11 for ; Wed, 10 Jul 2013 16:15:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:x-gm-message-state; bh=fFmSr+86bQmLUousP55vbCvEFuBbVLArpGEUoEoxMOQ=; b=iXrgbmbDwI+uqsRFIbBXl3MVGlPjNbIF3A21uPwq0hDTTtppLg4C7duwo8dHVxIHwW dKHjkh48tTkcxKjQ8YD1iJD0FYOR5cAJ+yHYHiJ5U8/V8mJxzybp2dPvIlbKZWIf1FJv ROsXtVSmxg8nJa4SFpEYxuoYK0YTTKS63wLnZ/1CEumabFnNXHM5l2vkBtxdv6nSoDYX /IEDjxLrgBxHw/on71/7kCJLQ1qNzDjq/K4KxcaiQTdoZq2lSPE7aYZk+TpbJDnSifBo KDSstC+XV6oGZXp+vHb4Y+qjZ/WBjIjy4SDjgx7xxDfxGKqdlQDCyPokoiCZDq7s8ZgL v3DA== X-Received: by 10.15.95.4 with SMTP id bc4mr38083282eeb.40.1373498132790; Wed, 10 Jul 2013 16:15:32 -0700 (PDT) X-Received: by 10.15.95.4 with SMTP id bc4mr38083275eeb.40.1373498132688; Wed, 10 Jul 2013 16:15:32 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id a4sm64114633eez.0.2013.07.10.16.15.30 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 16:15:31 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6ANFSpB014116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 11 Jul 2013 00:15:29 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6ANFSwG014115 for fortran@freebsd.org; Thu, 11 Jul 2013 00:15:28 +0100 (BST) (envelope-from mexas) Date: Thu, 11 Jul 2013 00:15:28 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307102315.r6ANFSwG014115@mech-cluster241.men.bris.ac.uk> To: fortran@freebsd.org Subject: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) X-Gm-Message-State: ALoCoQmWm2NeLkLMnsBQP5N/jENk/DOShebg4TmaiCbCdGMtlhBULc4KMRpxHhZ0IdRRYHqOqFXGHmteF7yFJpf8intfhJEL4h/A5iI/ueEHLvAKHoT8YImQcpobg4GitQXN/Ry0yOemJVhj7CVYx42eL+fjb0WNmw== X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 23:15:55 -0000 These errors are from french/aster on amd64. I think I need to rebuld lang/gcc after the recent updates to binutils, but anyway, which command line options to gfortran46 would lead to this error? These routines are GNU extensions specifically for complex(8), e.g.: http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gfortran/AIMAG.html#AIMAG Messages de compilation ======================= /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:34.18: IF (DIMAG(C).GT.0.D0) THEN 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:36.23: ELSE IF (DIMAG(C).LT.0.D0) THEN 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:42.34: DCARGU = DBLE(ATAN2(DIMAG(C),DBLE(C))) 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:44.34: DCARGU = DBLE(ATAN2(DIMAG(C),DBLE(C))) + PI 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/diaghr.f:89.45: IF (DBLE(SCALE).NE.0.0D0 .OR. DIMAG(SCALE).NE.0.0D0) 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/diares.f:46.35: CALL ZMULT (NEVEC, DCONJG(TAU(J)), EVEC(J,1), LDEVEC) 1 Error: Type of argument 'z' in call to 'dconjg' at (1) should be COMPLEX(16), not COMPLEX(8) /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/diares.f:51.23: DELTA = DIMAG(A(NR,NR))*ABS(A(NR,NR-1)) 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) From owner-freebsd-fortran@FreeBSD.ORG Wed Jul 10 23:27:46 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 11E029DA for ; Wed, 10 Jul 2013 23:27:46 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id D0B541133 for ; Wed, 10 Jul 2013 23:27:45 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6ANRfmY061979; Wed, 10 Jul 2013 16:27:41 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6ANRfOX061978; Wed, 10 Jul 2013 16:27:41 -0700 (PDT) (envelope-from sgk) Date: Wed, 10 Jul 2013 16:27:41 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) Message-ID: <20130710232741.GA61961@troutmask.apl.washington.edu> References: <201307102315.r6ANFSwG014115@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307102315.r6ANFSwG014115@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 23:27:46 -0000 On Thu, Jul 11, 2013 at 12:15:28AM +0100, Anton Shterenlikht wrote: > These errors are from french/aster on amd64. > I think I need to rebuld lang/gcc after the > recent updates to binutils, but anyway, > which command line options to gfortran46 > would lead to this error? > > These routines are GNU extensions specifically for complex(8), > e.g.: http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gfortran/AIMAG.html#AIMAG > > Messages de compilation > ======================= > /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:34.18: > > IF (DIMAG(C).GT.0.D0) THEN > 1 > Error: Type of argument 'z' in call to 'dimag' at (1) should > be COMPLEX(16), not COMPLEX(8) Need to see the declaration for C. My guess is that it is declared as 'complex c' or 'complex*8 c'. In either case, this is the single precision complex type. The program is using the specific intrinsic function dimag, which expects a double precision complex argument. The correct fixes are to properly declare the variables via Fortran's kind type parameter and to use generic intrinsic functions. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Thu Jul 11 08:09:29 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0D2948A4 for ; Thu, 11 Jul 2013 08:09:29 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog117.obsmtp.com (eu1sys200aog117.obsmtp.com [207.126.144.143]) by mx1.freebsd.org (Postfix) with ESMTP id 607131990 for ; Thu, 11 Jul 2013 08:09:28 +0000 (UTC) Received: from mail-ea0-f176.google.com ([209.85.215.176]) (using TLSv1) by eu1sys200aob117.postini.com ([207.126.147.11]) with SMTP ID DSNKUd5oNwAlEu/lRgrWR5U5xHDjf0qHq3OK@postini.com; Thu, 11 Jul 2013 08:09:28 UTC Received: by mail-ea0-f176.google.com with SMTP id z15so5472243ead.35 for ; Thu, 11 Jul 2013 01:09:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=jpBK4roiXTRoSN5r4r+TY1rkQnj/VK1dABj9znS9lf4=; b=QRb1bfAKrmaNqoh0Jc+AbNc6UAC7/1pZfsCMQZq83EKByrcBMVKVJkoa2Bwxx9Aqhd 5f0EG9H6n5I/FJrGb11+KjsKjeyH7nUUjVp2xnburvDp2SGueKBMzSQ2pR665jl0nAj/ hQH+e3c5VTm1DjfvnnyGId1xVM2stMqpVsrpAyfkx/Z+E1zD+ENJwCfJGpn/CJijQasD opkhFnMfHDGvcVfIqUbYeuQkQA6olScpDxAiTH15xaNygxgHsYbXfHzYXHN8YVrSRRvn fgJIQfnjFT0PHtW3KGG7/w+dTWjXWPb0/0toKjzOEcSBuAHX/XySQLQOK9xzWi1LlQ9y hMqQ== X-Received: by 10.14.241.5 with SMTP id f5mr40567120eer.131.1373530166885; Thu, 11 Jul 2013 01:09:26 -0700 (PDT) X-Received: by 10.14.241.5 with SMTP id f5mr40567101eer.131.1373530166771; Thu, 11 Jul 2013 01:09:26 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id w43sm67030772eez.6.2013.07.11.01.09.24 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 01:09:25 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6B89MR5022262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Jul 2013 09:09:22 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6B89Mwm022261; Thu, 11 Jul 2013 09:09:22 +0100 (BST) (envelope-from mexas) Date: Thu, 11 Jul 2013 09:09:22 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307110809.r6B89Mwm022261@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) In-Reply-To: <20130710232741.GA61961@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQlb/ucrncHkCFKSoYBJ7EqD2OPnTBqn0akFFLaFNO4USrZpV2PH6kaIppqPVjhd3LP1Z/5qfOhNJc2wPV63ucboMpxQcBzvgv9x8TxpC2UCOrp+A/2H7B6vGJUrro5mfpIb20qeOCEAFjrSEsNU81ZCCQwzmQ== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 08:09:29 -0000 From sgk@troutmask.apl.washington.edu Thu Jul 11 02:17:08 2013 On Thu, Jul 11, 2013 at 12:15:28AM +0100, Anton Shterenlikht wrote: > These errors are from french/aster on amd64. > I think I need to rebuld lang/gcc after the > recent updates to binutils, but anyway, > which command line options to gfortran46 > would lead to this error? > > These routines are GNU extensions specifically for complex(8), > e.g.: http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gfortran/AIMAG.html#AIMAG > > Messages de compilation > ======================= > /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/STA10.8/bibfor/algeline/dcargu.f:34.18: > > IF (DIMAG(C).GT.0.D0) THEN > 1 > Error: Type of argument 'z' in call to 'dimag' at (1) should > be COMPLEX(16), not COMPLEX(8) Need to see the declaration for C. My guess is that it is declared as 'complex c' or 'complex*8 c'. In either case, this is the single precision complex type. The program is using the specific intrinsic function dimag, which expects a double precision complex argument. The correct fixes are to properly declare the variables via Fortran's kind type parameter and to use generic intrinsic functions. $ cat dcargu.f FUNCTION DCARGU(C) IMPLICIT REAL*8 (A-H,O-Z) C----------------------------------------------------------------------- C CONFIGURATION MANAGEMENT OF EDF VERSION C MODIF ALGELINE DATE 14/11/2006 AUTEUR LEBOUVIER F.LEBOUVIER C ====================================================================== C COPYRIGHT (C) 1991 - 2001 EDF R&D WWW.CODE-ASTER.ORG C THIS PROGRAM IS FREE SOFTWARE; YOU CAN REDISTRIBUTE IT AND/OR MODIFY C IT UNDER THE TERMS OF THE GNU GENERAL PUBLIC LICENSE AS PUBLISHED BY C THE FREE SOFTWARE FOUNDATION; EITHER VERSION 2 OF THE LICENSE, OR C (AT YOUR OPTION) ANY LATER VERSION. C C THIS PROGRAM IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT C WITHOUT ANY WARRANTY; WITHOUT EVEN THE IMPLIED WARRANTY OF C MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SEE THE GNU C GENERAL PUBLIC LICENSE FOR MORE DETAILS. C C YOU SHOULD HAVE RECEIVED A COPY OF THE GNU GENERAL PUBLIC LICENSE C ALONG WITH THIS PROGRAM; IF NOT, WRITE TO EDF R&D CODE_ASTER, C 1 AVENUE DU GENERAL DE GAULLE, 92141 CLAMART CEDEX, FRANCE. C ====================================================================== C----------------------------------------------------------------------- C CALCUL DE L'ARGUMENT D'UN NOMBRE COMPLEXE C PAR CONVENTION ON AFFECTE 0.D0 SI C = (0.D0,0.D0) C----------------------------------------------------------------------- C IN : C : NOMBRE COMPLEXE DONT ON VEUT CALCULER L'ARGUMENT C----------------------------------------------------------------------- REAL*8 DCARGU COMPLEX*16 C C----------------------------------------------------------------------- PI = R8PI() C IF (DBLE(C).EQ.0.D0) THEN IF (DIMAG(C).GT.0.D0) THEN DCARGU = PI/2.D0 ELSE IF (DIMAG(C).LT.0.D0) THEN DCARGU = -PI/2.D0 ELSE DCARGU = 0.D0 ENDIF ELSE IF (DBLE(C).GT.0.D0) THEN DCARGU = DBLE(ATAN2(DIMAG(C),DBLE(C))) ELSE IF (DBLE(C).LT.0.D0) THEN DCARGU = DBLE(ATAN2(DIMAG(C),DBLE(C))) + PI ENDIF IF (DCARGU.LT.0.D0) DCARGU = DCARGU + 2.D0*PI C END $ $ gfortran46 -Wall -c dcargu.f $ So my guess is that in the port build, some other compiler options are used that cause the failure. I need to check this. And I've rebuilt binutils, lang/gcc, math/metis-edf (with the proposed patch). Also, french/aster builds fine on ia64 -current. Anton From owner-freebsd-fortran@FreeBSD.ORG Thu Jul 11 17:25:53 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E0C97412 for ; Thu, 11 Jul 2013 17:25:53 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id C4FD61B98 for ; Thu, 11 Jul 2013 17:25:53 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6BHPgkc067068; Thu, 11 Jul 2013 10:25:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6BHPgY2067067; Thu, 11 Jul 2013 10:25:42 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Jul 2013 10:25:42 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) Message-ID: <20130711172542.GA67029@troutmask.apl.washington.edu> References: <20130710232741.GA61961@troutmask.apl.washington.edu> <201307110809.r6B89Mwm022261@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307110809.r6B89Mwm022261@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 17:25:53 -0000 On Thu, Jul 11, 2013 at 09:09:22AM +0100, Anton Shterenlikht wrote: > From sgk@troutmask.apl.washington.edu Thu Jul 11 02:17:08 2013 > >On Thu, Jul 11, 2013 at 12:15:28AM +0100, Anton Shterenlikht wrote: >> These errors are from french/aster on amd64. >> I think I need to rebuld lang/gcc after the >> recent updates to binutils, but anyway, >> which command line options to gfortran46 >> would lead to this error? >> >> These routines are GNU extensions specifically for complex(8), >> e.g.: http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gfortran/AIMAG.html#AIMAG >> >> Messages de compilation >> ======================= >> /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/\ >> STA10.8/bibfor/algeline/dcargu.f:34.18: >> >> IF (DIMAG(C).GT.0.D0) THEN >> 1 >> Error: Type of argument 'z' in call to 'dimag' at (1) should >> be COMPLEX(16), not COMPLEX(8) > >Need to see the declaration for C. My guess is that it is declared >as 'complex c' or 'complex*8 c'. In either case, this is the single >precision complex type. The program is using the specific intrinsic >function dimag, which expects a double precision complex argument. > >The correct fixes are to properly declare the variables via Fortran's >kind type parameter and to use generic intrinsic functions. Please fix the quoting mechanism of your email client to NOT use tab characters. It leads to alot of wasted screen real estate. >$ cat dcargu.f > FUNCTION DCARGU(C) > IMPLICIT REAL*8 (A-H,O-Z) > REAL*8 DCARGU > COMPLEX*16 C > IF (DIMAG(C).GT.0.D0) THEN I suspect you are being hit by -fdefault-real-8 or similar option. If this is the case, you may want to ask the ASTER developers if they know what that option actually does. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Thu Jul 11 17:39:52 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8E9FD647 for ; Thu, 11 Jul 2013 17:39:52 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog110.obsmtp.com (eu1sys200aog110.obsmtp.com [207.126.144.129]) by mx1.freebsd.org (Postfix) with ESMTP id 78D031C21 for ; Thu, 11 Jul 2013 17:39:50 +0000 (UTC) Received: from mail-ea0-f171.google.com ([209.85.215.171]) (using TLSv1) by eu1sys200aob110.postini.com ([207.126.147.11]) with SMTP ID DSNKUd7tyuAKol5MikpmCfG61nvuN8Y3Xm3L@postini.com; Thu, 11 Jul 2013 17:39:51 UTC Received: by mail-ea0-f171.google.com with SMTP id m14so5897807eaj.30 for ; Thu, 11 Jul 2013 10:39:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=En4WlM5kd+z1ozDwSbUYj6JpE2yzIiFdaOhfRhnU6uE=; b=dEonaHFIBieVq9CfW/9gRew0nWEgYZPifDzLensm4SOD3OjaBRiGz2/SlVreasNT9X qSh+mPUDxIVl7I3RUQc8i6SsoakL/xoBoYCk5Y4KajLE4QZvr7fGvl+Wz+K0lJIf6Yq2 7ldEv7Vmijadw+pHkCpql5iHzGem0qxrfcNCVWFjU+n4MU0CKhWaGyGgLKDiksqOSocQ gxmwWe8Pm3zT9prI/qz0a38G5pZZXeqHYVB311n3Xyf79iAkKGnv7vzpemx9IllGjsga 9uWTIC5VXz2Mw9aSM+3nu1ZUs5nHqFBXNXJw9Z6XGQKl+4bzffE7MUuAFt6CovSf4XmK QdeQ== X-Received: by 10.15.35.129 with SMTP id g1mr43129211eev.2.1373564362256; Thu, 11 Jul 2013 10:39:22 -0700 (PDT) X-Received: by 10.15.35.129 with SMTP id g1mr43129201eev.2.1373564362171; Thu, 11 Jul 2013 10:39:22 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id n45sm70852896eew.1.2013.07.11.10.39.20 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 10:39:20 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6BHdIOI089383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Jul 2013 18:39:18 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6BHdI4E089382; Thu, 11 Jul 2013 18:39:18 +0100 (BST) (envelope-from mexas) Date: Thu, 11 Jul 2013 18:39:18 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307111739.r6BHdI4E089382@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) In-Reply-To: <20130711172542.GA67029@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQnHNqOdyOcLG8ee7RfLdh2iMEKmXISUuuqDybOCHNuW3AvrerKs9hnU6qSd6y5qn0E+KqaRHGDmReKKf15GqPfvApavjIDALdja9MYXtDRssw1Liy88jQflQ/BNudQDAjImxjyXe5LaIWEr3txOmPX90+SZ6g== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 17:39:52 -0000 >From sgk@troutmask.apl.washington.edu Thu Jul 11 18:32:18 2013 >On Thu, Jul 11, 2013 at 09:09:22AM +0100, Anton Shterenlikht wrote: >> From sgk@troutmask.apl.washington.edu Thu Jul 11 02:17:08 2013 >> >>On Thu, Jul 11, 2013 at 12:15:28AM +0100, Anton Shterenlikht wrote: >>> These errors are from french/aster on amd64. >>> I think I need to rebuld lang/gcc after the >>> recent updates to binutils, but anyway, >>> which command line options to gfortran46 >>> would lead to this error? >>> >>> These routines are GNU extensions specifically for complex(8), >>> e.g.: http://gcc.gnu.org/onlinedocs/gcc-4.6.4/gfortran/AIMAG.html#AIMAG >>> >>> Messages de compilation >>> ======================= >>> /usr/ports/french/aster/work/aster-full-src-10.8.0/instdir/\ >>> STA10.8/bibfor/algeline/dcargu.f:34.18: >>> >>> IF (DIMAG(C).GT.0.D0) THEN >>> 1 >>> Error: Type of argument 'z' in call to 'dimag' at (1) should >>> be COMPLEX(16), not COMPLEX(8) >> >>Need to see the declaration for C. My guess is that it is declared >>as 'complex c' or 'complex*8 c'. In either case, this is the single >>precision complex type. The program is using the specific intrinsic >>function dimag, which expects a double precision complex argument. >> >>The correct fixes are to properly declare the variables via Fortran's >>kind type parameter and to use generic intrinsic functions. > >Please fix the quoting mechanism of your email client to >NOT use tab characters. It leads to alot of wasted screen >real estate. as you wish... I use mail(1). I wonder why its developers thought that tab is a good default. > >>$ cat dcargu.f >> FUNCTION DCARGU(C) >> IMPLICIT REAL*8 (A-H,O-Z) >> REAL*8 DCARGU >> COMPLEX*16 C > >> IF (DIMAG(C).GT.0.D0) THEN > >I suspect you are being hit by -fdefault-real-8 or >similar option. If this is the case, you may want >to ask the ASTER developers if they know what that >option actually does. That's what I thought. I'll find exactly what options they use. Thanks Anton From owner-freebsd-fortran@FreeBSD.ORG Thu Jul 11 23:49:50 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 37B3BEA1 for ; Thu, 11 Jul 2013 23:49:50 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog110.obsmtp.com (eu1sys200aog110.obsmtp.com [207.126.144.129]) by mx1.freebsd.org (Postfix) with ESMTP id B54B51E02 for ; Thu, 11 Jul 2013 23:49:48 +0000 (UTC) Received: from mail-ee0-f41.google.com ([74.125.83.41]) (using TLSv1) by eu1sys200aob110.postini.com ([207.126.147.11]) with SMTP ID DSNKUd9EmBpuoFeyr90nVzjIZR6QGzv6Qah1@postini.com; Thu, 11 Jul 2013 23:49:48 UTC Received: by mail-ee0-f41.google.com with SMTP id d17so5968763eek.28 for ; Thu, 11 Jul 2013 16:49:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=/81rGeKi6nS6i8bQRjtWV7lLlV1A1E8p/DGUbmbteyc=; b=p3Vs/P3SDPq7YWkzbnDMoCXlktSLUIZolGxUZotFCLiQSEBcccBU/eLsVMnBEnDrHs o9SMTjvOTRQm67jdUMu4bImG8f6Hkrh+bsKg2iZuf8gAcUyC5MRrNLKWQLM/K1XJCukI PsJnGrTJ8u2rGgfreJyBceyOaBFRCRIWQL3eMFtEqT7FoYBEYjDZmqrId6Fy53QzV1YO ZO+uCM7unfrfRRYL0mO6oCcH/AC/Md9RWQRzgYapUYQyNtXa6KsntIaBid75Zwej8+FE 0ObpdgmWn/OoHxcMdQ0gy1I8dQIGM8TZBIPJl2DTr03hO4BmA1O9PYMyUdQf0hIfpQyV saoA== X-Received: by 10.15.64.68 with SMTP id n44mr39579059eex.73.1373586127372; Thu, 11 Jul 2013 16:42:07 -0700 (PDT) X-Received: by 10.15.64.68 with SMTP id n44mr39579052eex.73.1373586127274; Thu, 11 Jul 2013 16:42:07 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id i2sm73363535eeu.4.2013.07.11.16.42.05 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 16:42:06 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6BNg3L3090241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jul 2013 00:42:04 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6BNg32L090240; Fri, 12 Jul 2013 00:42:03 +0100 (BST) (envelope-from mexas) Date: Fri, 12 Jul 2013 00:42:03 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307112342.r6BNg32L090240@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu, thierry@FreeBSD.org Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) In-Reply-To: <20130711172542.GA67029@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQlUXF0znMIcVHBHLNC3MaG06aPvjlukPH2hAJ6AQK15KaKLtpkUKeIIux1a7fouOeZL35lhrI+WZqL56Li0xT4gqdtqhFcfBvVDbxscQOpYrB+C2CHiZbKoxymCETHbYLPiL1fcFeXBkqvqIfBvok88wioKmw== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 23:49:50 -0000 >From sgk@troutmask.apl.washington.edu Thu Jul 11 18:32:18 2013 >> >>The correct fixes are to properly declare the variables via Fortran's >>kind type parameter and to use generic intrinsic functions. > >Please fix the quoting mechanism of your email client to >NOT use tab characters. It leads to alot of wasted screen >real estate. > >>$ cat dcargu.f >> FUNCTION DCARGU(C) >> IMPLICIT REAL*8 (A-H,O-Z) >> REAL*8 DCARGU >> COMPLEX*16 C > >> IF (DIMAG(C).GT.0.D0) THEN > >I suspect you are being hit by -fdefault-real-8 or >similar option. If this is the case, you may want >to ask the ASTER developers if they know what that >option actually does. (cc to thierry@ - the maintainer) It's actually in the port's Makefile: .if ${ARCH} == "i386" FLAGARCH= -DP_LINUX -DLINUX FFLAGARCH= .else FLAGARCH= -DLINUX64 FFLAGARCH= -fdefault-integer-8 -fdefault-real-8 .endif Anyway, please correct my analysis if it's wrong. complex*16 is the same as complex(kind=8), meaning 16 bytes total, or two 8-byte reals. The effect of -fdefault-real-8 is to make DIMAG expect not complex(8) but complex(16), but *only* on platforms where complex(16) is supported. And on ia64 is does not seem to be supported, and -fdefault-real8 has no effect on ia64: $ uname -a FreeBSD mech-cluster241.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r252055: Fri Jun 21 15:57:18 BST 2013 root@mech-cluster241.men.bris.ac.uk:/usr/obj/usr/src/sys/TZAV ia64 $ cat z.f90 complex*16 :: z z = (1,2) write (*,*) dimag(z) end $ gfortran46 -Wall z.f90 $ ./a.out 2.0000000000000000 $ gfortran46 -Wall -fdefault-real-8 z.f90 $ ./a.out 2.0000000000000000 $ In contract, on amd64, -fdefault-real-8 makes DIMAG expect complex(16), but complex(8) is given. And changing the declaration to complex(16) makes the code compile and work as expected, i.e. increase the number of significant digits roughly by a factor of 2: $ cat z.f90 complex*16 :: z z = (1,2) write (*,*) dimag(z) end $ gfortran46 z.f90 $ ./a.out 2.0000000000000000 $ gfortran46 -fdefault-real-8 z.f90 z.f90:3.18: write (*,*) dimag(z) 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) $ sed s/\*16/\(kind=16\)/g z.f90 > zz.f90 $ cat zz.f90 complex(kind=16) :: z z = (1,2) write (*,*) dimag(z) end $ gfortran46 zz.f90 zz.f90:3.18: write (*,*) dimag(z) 1 Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(8), not COMPLEX(16) $ gfortran46 -fdefault-real-8 zz.f90 $ ./a.out 2.0000000000000000000000000000000000 $ Anyway, it is important to know that -fdefault-real-8 does not affect the complex declarations. I agree with you that this routine from the Aster code is not very well written, i.e. is not written with portability in mind. However, code_Aster is massive and I don't think it likely the developers will want to fix issues like this. I'm not sure what to do about this. Anton From owner-freebsd-fortran@FreeBSD.ORG Fri Jul 12 05:14:22 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 11AB59F9; Fri, 12 Jul 2013 05:14:22 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id CFE2E19ED; Fri, 12 Jul 2013 05:14:21 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6C5EIxo071143; Thu, 11 Jul 2013 22:14:18 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6C5EHR0071142; Thu, 11 Jul 2013 22:14:17 -0700 (PDT) (envelope-from sgk) Date: Thu, 11 Jul 2013 22:14:17 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) Message-ID: <20130712051417.GA71107@troutmask.apl.washington.edu> References: <20130711172542.GA67029@troutmask.apl.washington.edu> <201307112342.r6BNg32L090240@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307112342.r6BNg32L090240@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 05:14:22 -0000 On Fri, Jul 12, 2013 at 12:42:03AM +0100, Anton Shterenlikht wrote: >>From sgk@troutmask.apl.washington.edu Thu Jul 11 18:32:18 2013 >> >>>$ cat dcargu.f >>> FUNCTION DCARGU(C) >>> IMPLICIT REAL*8 (A-H,O-Z) >>> REAL*8 DCARGU >>> COMPLEX*16 C >> >>> IF (DIMAG(C).GT.0.D0) THEN >> >>I suspect you are being hit by -fdefault-real-8 or >>similar option. If this is the case, you may want >>to ask the ASTER developers if they know what that >>option actually does. > > (cc to thierry@ - the maintainer) > > It's actually in the port's Makefile: > > .if ${ARCH} == "i386" > FLAGARCH= -DP_LINUX -DLINUX > FFLAGARCH= > .else > FLAGARCH= -DLINUX64 > FFLAGARCH= -fdefault-integer-8 -fdefault-real-8 > .endif > > Anyway, please correct my analysis if it's wrong. > > complex*16 is the same as complex(kind=8), meaning > 16 bytes total, or two 8-byte reals. > The effect of -fdefault-real-8 is to make DIMAG > expect not complex(8) but complex(16), but *only* > on platforms where complex(16) is supported. Yes, this is essentially the cause of the problem. I downloaded french/aster, and quite frankly, I would not trust any results from that code. Given the amount of Fortran code, blindly using -fdefault-integer-8 and -fdefault-real-8 is not a good idea. > And on ia64 is does not seem to be supported, > and -fdefault-real8 has no effect on ia64: I don't have access to ia64, so can't look into gfortran's behavior. > $ cat z.f90 > complex*16 :: z > z = (1,2) > write (*,*) dimag(z) > end > $ gfortran46 -Wall z.f90 > $ ./a.out > 2.0000000000000000 > $ gfortran46 -Wall -fdefault-real-8 z.f90 > $ ./a.out > 2.0000000000000000 You need to look at -fdump-tree-original. This produces gcc's intermediate code, and may show the promotion. > I agree with you that this routine from the > Aster code is not very well written, i.e. > is not written with portability in mind. > However, code_Aster is massive and I don't think > it likely the developers will want to fix > issues like this. I suspect that the code_aster developers have no idea how dangerous these options are, or understand their limitations. If the code_aster developers do not want to do a proper port of the Fortran code from single precision to double precision, then they probably should use -freal-4-real-8, which is likely closers to what they want. -- Steve From owner-freebsd-fortran@FreeBSD.ORG Fri Jul 12 11:05:40 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87C573E8 for ; Fri, 12 Jul 2013 11:05:40 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog122.obsmtp.com (eu1sys200aog122.obsmtp.com [207.126.144.153]) by mx1.freebsd.org (Postfix) with ESMTP id DEB581D68 for ; Fri, 12 Jul 2013 11:05:39 +0000 (UTC) Received: from mail-ee0-f54.google.com ([74.125.83.54]) (using TLSv1) by eu1sys200aob122.postini.com ([207.126.147.11]) with SMTP ID DSNKUd/i5sh1k0RuuwZe9Mzx5bPy7wLuA7q2@postini.com; Fri, 12 Jul 2013 11:05:39 UTC Received: by mail-ee0-f54.google.com with SMTP id t10so6159256eei.41 for ; Fri, 12 Jul 2013 04:05:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=oAayELw07zs0xGjSZDsGGwnDhHS/u4kdv/k3a2/2oKE=; b=UDUokmGmM84Gkx5wOirrErViCOekVUMzXbzFnD+9k/n/oxxiGzUmYkedDlWrCni3lj Ww0vQ4HzE2RKgBcmrHhL+nbDIqvejv59HXL4722gcGl1rYqqAJyhhFgHeWUvOI8BHQ4+ pLpIMAeb1gMjg4tUogi1bOecR6paxghXHT+IAr/KkpIGhjoHKL73OFNKHvIz90g+YQOe 0XrMl2sYqAQVdA4NxtDTWgshwwW00gBU2RyU78E5n9sDKn7Asr6amMDMBbbz5OJCOeMT /CAHcbQPzifan85FamWRAUi9iNEssY/tKq1KT9tuUJhndkXRhl6VrO3JZ5W4ZK5wWBLe BTVw== X-Received: by 10.14.95.69 with SMTP id o45mr46760246eef.48.1373627110798; Fri, 12 Jul 2013 04:05:10 -0700 (PDT) X-Received: by 10.14.95.69 with SMTP id o45mr46760241eef.48.1373627110722; Fri, 12 Jul 2013 04:05:10 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id c3sm13998538eev.3.2013.07.12.04.05.08 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 04:05:09 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6CB57EV098855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jul 2013 12:05:07 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6CB57qE098854; Fri, 12 Jul 2013 12:05:07 +0100 (BST) (envelope-from mexas) Date: Fri, 12 Jul 2013 12:05:07 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307121105.r6CB57qE098854@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) In-Reply-To: <20130712051417.GA71107@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQli7nkMOE7MOPjsgct445/dikZ69NpOwyuTOsNtcJA4KYOEAp0o+3NkTd1fb5bL9lzFNCEAYUrZ6dtyDBy9ExmSo7U2L66mcsiVn8TMXiXNPhElbyZEWGfNKER1k9Q9exo/MbWfgUgxOs2hKcZq43xVbaUz+A== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 11:05:40 -0000 >From sgk@troutmask.apl.washington.edu Fri Jul 12 07:25:06 2013 > >You need to look at -fdump-tree-original. >This produces gcc's intermediate code, and >may show the promotion. on ia64 the intermediate code is identical with and without -fdefault-real-8: $ cat z.f90 complex*16 :: z z = (1,2) write (*,*) dimag(z) end $ gfortran46 -fdump-tree-original z.f90 $ mv z.f90.003t.original z1 $ gfortran46 -fdump-tree-original -fdefault-real-8 z.f90 $ diff z.f90.003t.original z1 $ cat z.f90.003t.original MAIN__ () { complex(kind=8) z; z = __complex__ (1.0e+0, 2.0e+0); { struct __st_parameter_dt dt_parm.0; dt_parm.0.common.filename = &"z.f90"[1]{lb: 1 sz: 1}; dt_parm.0.common.line = 3; dt_parm.0.common.flags = 128; dt_parm.0.common.unit = 6; _gfortran_st_write (&dt_parm.0); { real(kind=8) D.719; D.719 = IMAGPART_EXPR ; _gfortran_transfer_real_write (&dt_parm.0, &D.719, 8); } _gfortran_st_write_done (&dt_parm.0); } } main (integer(kind=4) argc, character(kind=1) * * argv) { static integer(kind=4) options.1[8] = {68, 511, 0, 0, 0, 1, 0, 1}; _gfortran_set_args (argc, argv); _gfortran_set_options (8, &options.1[0]); MAIN__ (); return 0; } $ Anton From owner-freebsd-fortran@FreeBSD.ORG Fri Jul 12 11:18:56 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EDF98695 for ; Fri, 12 Jul 2013 11:18:56 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog103.obsmtp.com (eu1sys200aog103.obsmtp.com [207.126.144.115]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED611DF3 for ; Fri, 12 Jul 2013 11:18:55 +0000 (UTC) Received: from mail-ea0-f175.google.com ([209.85.215.175]) (using TLSv1) by eu1sys200aob103.postini.com ([207.126.147.11]) with SMTP ID DSNKUd/mGZvPIo0ik654RsprG73CrBB+YIqY@postini.com; Fri, 12 Jul 2013 11:18:56 UTC Received: by mail-ea0-f175.google.com with SMTP id z7so6283558eaf.34 for ; Fri, 12 Jul 2013 04:18:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:cc:reply-to:in-reply-to :x-gm-message-state; bh=D+TUtgmkYMGG4BOiEJmdZ1HgeaEt6QCew6N2VUVI2eg=; b=IvMwK+tr0Xtl6sCc8LTin6Q/RpevPkKz3xMaDlvqM+NeGG/V5yr0vCbCu7/HCkP9HM SAFs7SVy9abxw404DwojWaD5ZeEd+iEhSkauQL2GlLBEa0YOD+LfAYwPpvVgQy1psuKE 3Z1Mk4VpJybYXzK+QKVYmTSAgZxMG6qtKtJfuqbRDqpN0o66UCSR74G3Hic+lFHJF764 6y6lZG6CPSerXfFqARuyJ9cJIitx6XaBSYYrUZbvX9/+QKbiLakQdcgPAr34lTVLaCCy XiX1o9Rv/ohcqv6AJYRSauHtRSWceHhmEQ+Jlc+pkMCpt7TIIqVmT1JF7oUyPfOvcEIn C1Mw== X-Received: by 10.14.223.199 with SMTP id v47mr46833233eep.32.1373627929359; Fri, 12 Jul 2013 04:18:49 -0700 (PDT) X-Received: by 10.14.223.199 with SMTP id v47mr46833139eep.32.1373627928005; Fri, 12 Jul 2013 04:18:48 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id l42sm77441225eeo.14.2013.07.12.04.18.46 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Jul 2013 04:18:46 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r6CBIirm098988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 12 Jul 2013 12:18:44 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r6CBIhiE098987; Fri, 12 Jul 2013 12:18:43 +0100 (BST) (envelope-from mexas) Date: Fri, 12 Jul 2013 12:18:43 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307121118.r6CBIhiE098987@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, sgk@troutmask.apl.washington.edu Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) In-Reply-To: <20130712051417.GA71107@troutmask.apl.washington.edu> X-Gm-Message-State: ALoCoQmkAzH7mOFh3vrdhC06aN5/o2Zs5GXx+HqL4WO/Z05C8H4dqniAd7Og0JWPX02xlHV4SP/dKAl7ycj6VvZxq3WvVOkncV8unbwGuA8/sDy9L9vUY/aGb8X2sJSXaVQFoWNnLUMMEeke8d7S4W6I/3TLgUyMwA== Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 11:18:57 -0000 >From sgk@troutmask.apl.washington.edu Fri Jul 12 07:25:06 2013 *skip* >Yes, this is essentially the cause of the problem. >I downloaded french/aster, and quite frankly, I >would not trust any results from that code. Given >the amount of Fortran code, blindly using >-fdefault-integer-8 and -fdefault-real-8 is not a >good idea. *skip* >I suspect that the code_aster developers have no >idea how dangerous these options are, or understand >their limitations. If the code_aster developers >do not want to do a proper port of the Fortran code >from single precision to double precision, then they >probably should use -freal-4-real-8, which is likely >closers to what they want. Ok, I'll see if the port builds with -freal-4-real-8. However this option is only supported starting from 4.7: $ gfortran46 -freal-4-real-8 z.f90 f951: error: unrecognized command line option '-freal-4-real-8' $ gfortran47 -freal-4-real-8 z.f90 $ which brings me to the topic I struggled for some time - using non-default GCC ports compiler. Simply changing $ grep GCC_DEFAULT_VERSION= /usr/ports/Mk/bsd.gcc.mk GCC_DEFAULT_VERSION= 4.6 $ to e.g. 4.7 seems to work for some ports but not for others. It is not clear how many ports, and which, have to be rebuilt with such a change. For example, if I want to build code_aster with 4.7, do I need to rebuild all or some ports on which it depends also with 4.7? Anton From owner-freebsd-fortran@FreeBSD.ORG Fri Jul 12 16:52:44 2013 Return-Path: Delivered-To: fortran@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C4B7B3B1; Fri, 12 Jul 2013 16:52:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8E5601021; Fri, 12 Jul 2013 16:52:44 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r6CGqeUL074369; Fri, 12 Jul 2013 09:52:40 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r6CGqd0w074368; Fri, 12 Jul 2013 09:52:39 -0700 (PDT) (envelope-from sgk) Date: Fri, 12 Jul 2013 09:52:39 -0700 From: Steve Kargl To: mexas@bristol.ac.uk Subject: Re: gfortran46: Error: Type of argument 'z' in call to 'dimag' at (1) should be COMPLEX(16), not COMPLEX(8) Message-ID: <20130712165239.GA74169@troutmask.apl.washington.edu> References: <20130712051417.GA71107@troutmask.apl.washington.edu> <201307121118.r6CBIhiE098987@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307121118.r6CBIhiE098987@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: fortran@freebsd.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jul 2013 16:52:44 -0000 On Fri, Jul 12, 2013 at 12:18:43PM +0100, Anton Shterenlikht wrote: > >From sgk@troutmask.apl.washington.edu Fri Jul 12 07:25:06 2013 > > >I suspect that the code_aster developers have no > >idea how dangerous these options are, or understand > >their limitations. If the code_aster developers > >do not want to do a proper port of the Fortran code > >from single precision to double precision, then they > >probably should use -freal-4-real-8, which is likely > >closers to what they want. > > Ok, I'll see if the port builds with -freal-4-real-8. > However this option is only supported starting from 4.7: > > $ gfortran46 -freal-4-real-8 z.f90 > f951: error: unrecognized command line option '-freal-4-real-8' > $ gfortran47 -freal-4-real-8 z.f90 > $ > > which brings me to the topic I struggled for some time - > using non-default GCC ports compiler. Simply changing > > $ grep GCC_DEFAULT_VERSION= /usr/ports/Mk/bsd.gcc.mk > GCC_DEFAULT_VERSION= 4.6 > $ > > to e.g. 4.7 seems to work for some ports but not for others. I would need to see the specific errors/issues. 4.7 of course fixes numerous bugs in 4.6, adds features, and may tighten up conformance checking. > It is not clear how many ports, and which, have to > be rebuilt with such a change. For example, if I want > to build code_aster with 4.7, do I need to rebuild > all or some ports on which it depends also with 4.7? IIRC, the ABI for the runtime library has not changed from 4.6 to 4.7. So, code compiled with 4.6 should be able to link with the 4.7 compiler. I don't remember if/what may have changed with module internals. Here's a slightly better example code for testing the options. Note, there are still some quirks one needs to understand about these options and Fortran's EQUIVALENCE, COMMON, and use of kind type parameter suffixes (ie., 1.e0_8). integer, parameter :: sp = kind(1.e0), dp = kind(1.d0) complex z ! Standard conforming default kind. complex(sp) zsp ! Standard conforming default kind. complex(dp) zdp ! Standard conforming double precision. complex*8 a8 ! Non-standard old school declaration complex*16 a16 ! Non-standard old school declaration print '(5(I0,1X))', kind(z), kind(zsp), kind(zdp), kind(a8), kind(a16) end This is on amd64. % gfc4x -o a a.f90 && ./a 4 4 8 4 8 % gfc4x -o a a.f90 -fdefault-real-8 && ./a 8 8 16 4 8 % gfc4x -o a a.f90 -freal-4-real-8 && ./a 8 8 8 8 8 -- Steve