(cc'ing macports-dev)
> The problem is actually with MacPorts 4.3.2. A little more accurately, this
> is NOT an actual bug. The problem is that the behavior you are seeing is
> allowed under the Fortran standard -- that's why selected_int_kind exists in
> the first place.
This is wrong. The Fo
Hello,
I don't understand the last comment of this mail.
Following IBM link its said:
Examples
SELECTED_INT_KIND (9) has the value 4, signifying that an INTEGER with
kind type 4 can represent all values from 10^-9 to 10^9 .
Regards
Le 27/04/12 08:02, Brandon Allbery a écrit :
On Fr
On Fri, Apr 27, 2012 at 01:14, Victor Eijkhout wrote:
> On Apr 26, 2012, at 11:22 PM, Jason Swails wrote:
> > The problem is that the behavior you are seeing is allowed under the
> Fortran standard
>
> I'll take your word for it. I ran into this when I compiling some software
> that used kind(5) a
On Apr 26, 2012, at 11:22 PM, Jason Swails wrote:
> The problem is that the behavior you are seeing is allowed under the Fortran
> standard
I'll take your word for it. I ran into this when I compiling some software that
used kind(5) as a synonym for INTEGER*4 (after all, 32k is 5 digits) and s
The problem is actually with MacPorts 4.3.2. A little more accurately, this is
NOT an actual bug. The problem is that the behavior you are seeing is allowed
under the Fortran standard -- that's why selected_int_kind exists in the first
place.
I had to issue a patch for a piece of software that
On Apr 26, 2012, at 9:58 PM, Ryan Schmidt wrote:
> Test with gcc47 and gcc48
I did, at least version 4.8. But the problem is that it behaves differently
with MacPorts than the gcc distribution on Linux, so the package maintainer for
gcc might know more about it.
Victor.
__
On Apr 26, 2012, at 20:02, Victor Eijkhout wrote:
> this may be more suited for the dev list….
I think we're probably not fortran experts here; you may have to ask the
developers of gcc instead. Test with gcc47 and gcc48 first of course to make
sure it's not a problem they've already fixed.
>
this may be more suited for the dev list….
I have a small fortran program that gives different (read: wrong) output on
macports from on linux.
[albook:~/Current/petsc-course/course20120514/fsolutions] %% gfortran --version
GNU Fortran (GCC) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc
