Re: gfortran with Xcode 4.3.2 unreliable
On Sun, Jun 10, 2012 at 7:49 AM, Vincent Habchi wrote: > On 10 juin 2012, at 09:08, Ryan Schmidt wrote: > > > This problem with the gmp port has already been fixed in r94119. > > Was there a new test suite applied after this patch? The conclusion we > must use llvm-gcc42 instead of clang seems to bear a relation with > something I noticed on Atlas (together with the maintainer), that is > (purely mathematical) code fails testing. As if the FP code produced by > clang was somehow buggy. > I've been using llvm-gcc42: Jasons-MacBook-Pro:~ swails$ port installed | grep -i clang Jasons-MacBook-Pro:~ swails$ Also, after doing a "port selfupdate" and "port upgrade outdated" (and just installing MacPorts from scratch) resolves the issue. Before the update: Jasons-MacBook-Pro:~ swails$ ./a.out selected_real_kind(15,307) = 10 selected_real_kind(6,37) =8 selected_real_kind(13,307) = 10 After the update: Jasons-MacBook-Pro:~ swails$ gfortran test.F90 Jasons-MacBook-Pro:~ swails$ ./a.out selected_real_kind(15,307) =8 selected_real_kind(6,37) =4 selected_real_kind(13,307) =8 This program was designed to test the behavior of selected_real_kind, and it now behaves properly. I can't report regarding clang, but llvm-gcc42 works fine. Thanks! Jason -- Jason M. Swails Quantum Theory Project, University of Florida Ph.D. Candidate 352-392-4032 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gfortran with Xcode 4.3.2 unreliable
On 10 juin 2012, at 09:08, Ryan Schmidt wrote: > This problem with the gmp port has already been fixed in r94119. Was there a new test suite applied after this patch? The conclusion we must use llvm-gcc42 instead of clang seems to bear a relation with something I noticed on Atlas (together with the maintainer), that is (purely mathematical) code fails testing. As if the FP code produced by clang was somehow buggy. Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gfortran with Xcode 4.3.2 unreliable
On Jun 10, 2012, at 02:00, Vincent Habchi wrote: >> However, a comprehensive test suite that tests out fine with GCC 4.2, 4.3, >> 4.4, 4.5, 4.6, and 4.7, along with all flavors of (buggy) intel fortran >> compilers, and the PGI compilers all fail with this particular gfortran >> build. I will look through your patch and see if it fixes my problems (this >> is affecting quite a few users of this program suite). If so, hopefully the >> port maintainer (or some other dev) can apply this fix, because just fixing >> it for me is not enough (I have the 10.6 SDK, so I'm not even affected by >> this). > > Are you using clang or llvm-gcc to compile gmp? This problem with the gmp port has already been fixed in r94119. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gfortran with Xcode 4.3.2 unreliable
> However, a comprehensive test suite that tests out fine with GCC 4.2, 4.3, > 4.4, 4.5, 4.6, and 4.7, along with all flavors of (buggy) intel fortran > compilers, and the PGI compilers all fail with this particular gfortran > build. I will look through your patch and see if it fixes my problems (this > is affecting quite a few users of this program suite). If so, hopefully the > port maintainer (or some other dev) can apply this fix, because just fixing > it for me is not enough (I have the 10.6 SDK, so I'm not even affected by > this). Are you using clang or llvm-gcc to compile gmp? Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gfortran with Xcode 4.3.2 unreliable
On Sat, Jun 9, 2012 at 1:47 PM, Sean Farley wrote: > > There was a thread ~1 month ago regarding gfortran that was acting > > strangely. Here's a link to that > > thread: > http://lists.macosforge.org/pipermail/macports-dev/2012-May/019098.html > > > > I haven't seen any responses or anything to this, and I was wondering if > > anyone else had run into issues trying to use gfortran from any of the > gcc4X > > builds using Xcode 4.3.x on Lion. > > > > There seems to be something *seriously* wrong with the Fortran compiler > > built with MacPorts -- in a very Fortran-heavy program suite, nearly > half of > > the tests are suddenly failing when built with these compilers even after > > the selected_real_kind() issues are resolved. And the failures are not > > blatantly ridiculous, they're subtle, but currently I'm wary of trusting > > anything the MacPorts-built GCC compilers (at least the Fortran > compilers) > > spit out. > > Yes, you are correct that this is seriously wrong and very subtle. The > issue is with gmp and causes gfortran to erroneously double the size > of (at least) ints. I opened a ticket here with a patch: > It's not just ints -- it's floats, too. reals are erroneously passed as doubles, and doubles as 10-byte floats (??), but only sometimes... It's hard to determine what exactly is happening (especially since I'm more of a user of programming and less of a pure programmer). However, a comprehensive test suite that tests out fine with GCC 4.2, 4.3, 4.4, 4.5, 4.6, and 4.7, along with all flavors of (buggy) intel fortran compilers, and the PGI compilers all fail with this particular gfortran build. I will look through your patch and see if it fixes my problems (this is affecting quite a few users of this program suite). If so, hopefully the port maintainer (or some other dev) can apply this fix, because just fixing it for me is not enough (I have the 10.6 SDK, so I'm not even affected by this). For what it's worth, the compilers on hpc.sourceforge.net appear to work just fine, but I'm not a fan of always using the bleeding-edge, latest-checkout-version of the compiler suite... It's bitten me on a couple of occasions. > https://trac.macports.org/ticket/34491 > > that fixes the gmp issue and also fixes debuggers loading shared > symbols; but haven't heard back from the macports devs at all on the > issue. You should be able to apply the patch yourself and rebuild > everything from source with the -s option: > > $ sudo port uninstall --follow-dependents gmp > $ sudo port -vs install gcc47 > > or whichever gcc you have installed. Hope that helps! > The debug symbols are great! Thanks for this! Jason -- Jason M. Swails Quantum Theory Project, University of Florida Ph.D. Candidate 352-392-4032 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gfortran with Xcode 4.3.2 unreliable
> There was a thread ~1 month ago regarding gfortran that was acting > strangely. Here's a link to that > thread: http://lists.macosforge.org/pipermail/macports-dev/2012-May/019098.html > > I haven't seen any responses or anything to this, and I was wondering if > anyone else had run into issues trying to use gfortran from any of the gcc4X > builds using Xcode 4.3.x on Lion. > > There seems to be something *seriously* wrong with the Fortran compiler > built with MacPorts -- in a very Fortran-heavy program suite, nearly half of > the tests are suddenly failing when built with these compilers even after > the selected_real_kind() issues are resolved. And the failures are not > blatantly ridiculous, they're subtle, but currently I'm wary of trusting > anything the MacPorts-built GCC compilers (at least the Fortran compilers) > spit out. Yes, you are correct that this is seriously wrong and very subtle. The issue is with gmp and causes gfortran to erroneously double the size of (at least) ints. I opened a ticket here with a patch: https://trac.macports.org/ticket/34491 that fixes the gmp issue and also fixes debuggers loading shared symbols; but haven't heard back from the macports devs at all on the issue. You should be able to apply the patch yourself and rebuild everything from source with the -s option: $ sudo port uninstall --follow-dependents gmp $ sudo port -vs install gcc47 or whichever gcc you have installed. Hope that helps! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
gfortran with Xcode 4.3.2 unreliable
Hello, There was a thread ~1 month ago regarding gfortran that was acting strangely. Here's a link to that thread: http://lists.macosforge.org/pipermail/macports-dev/2012-May/019098.html I haven't seen any responses or anything to this, and I was wondering if anyone else had run into issues trying to use gfortran from any of the gcc4X builds using Xcode 4.3.x on Lion. There seems to be something *seriously* wrong with the Fortran compiler built with MacPorts -- in a very Fortran-heavy program suite, nearly half of the tests are suddenly failing when built with these compilers even after the selected_real_kind() issues are resolved. And the failures are not blatantly ridiculous, they're subtle, but currently I'm wary of trusting anything the MacPorts-built GCC compilers (at least the Fortran compilers) spit out. Thanks! Jason -- Jason M. Swails Quantum Theory Project, University of Florida Ph.D. Candidate 352-392-4032 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
