|
|
 Up |
|
|
  |
Author: Arjen MarkusArjen Markus Date: Sep 18, 2008 23:48
On 18 sep, 23:41, steven.bossc...@ gmail.com wrote: >
> You have to realize that not a single one of the gfortran developers
> (current and past, including g95) have a computer science background.
> At least, not as far as I know.
>
> All gfortran developers are physicists, engineers, mathematicians,
> etc., in their Real Life, just like most people that follow this
> newsgroup. These developers started as Fortran users, with no more
> knowledge of compiler construction than most people here.
>
I definitely qualify as such: I am a physicist by training and
even though day job concerns the development and maintaince of
programs in a number of languages, physics and engineering (most
notably the numerical modelling of the phenomena) remain my
prime interest.
Regards,
Arjen
|
| |
|
| | no comments |
|
|
Author: tholentholen Date: Sep 19, 2008 02:27
> I think the typical way one gets deeply involved with gfortran
> development is as follows:
I'm interested in seeing gfortran ported to another operating
system. I'm assuming that gfortran itself is written in C or
some variant of C, which means a prerequisite is having a C
compiler for that operating system, but as far as I know, the
available version of the gnu C compiler is too old. Perhaps
someone can list the steps necessary to port gfortran to
another operating system.
|
| |
|
| | no comments |
|
|
Author: Tobias BurnusTobias Burnus Date: Sep 19, 2008 04:29
On Sep 19, 11:27 am, "tho...@antispam.ham" ifa.hawaii.edu>
wrote:>> I think the typical way one gets deeply involved with gfortran
>> development is as follows:
>
> I'm interested in seeing gfortran ported to another operating
> system. I'm assuming that gfortran itself is written in C or
> some variant of C, which means a prerequisite is having a C
> compiler for that operating system, but as far as I know, the
> available version of the gnu C compiler is too old. Perhaps
> someone can list the steps necessary to port gfortran to
> another operating system.
If I understand it correctly, you have a system on which an older
"gcc" works, but it is too old to compile the current GCC. Assuming
that GCC is still supported on that platform, you should try to find
the newest GCC which still compiles with your old GCC (or any other C
compiler) and then use the newer GCC to compile GCC 4.4. (Another
possibility is to build an cross-compiler.)
|
| Show full article (2.43Kb) |
| no comments |
|
|
Author: Carlie J. CoatsCarlie J. Coats Date: Sep 19, 2008 05:15
Al Greynolds wrote:
> Over the last few years I have developed a 30,000 line Fortran-95
> engineering application using simultaneously several compilers (XLF,
> LF95, G95, and IVF). During that time I toyed with Gfortran and put
> up with the 2 steps forward, 1 step back of each binary build.
> However, I'm now happy to report my "last" issue with it has been
> resolved and more importantly performance is almost identical to XLF
> and IVF in most cases. Congratulations to all involved with this
> project!
>
> Al Greynolds
> www.ruda.com
|
| Show full article (1.98Kb) |
| no comments |
|
|
Author: Arjen MarkusArjen Markus Date: Sep 19, 2008 05:41
On 19 sep, 14:15, "Carlie J. Coats" jyarborough.com> wrote:> Al Greynolds wrote:
>> Over the last few years I have developed a 30,000 line Fortran-95
>> engineering application using simultaneously several compilers (XLF,
>> LF95, G95, and IVF). During that time I toyed with Gfortran and put
>> up with the 2 steps forward, 1 step back of each binary build.
>> However, I'm now happy to report my "last" issue with it has been
>> resolved and more importantly performance is almost identical to XLF
>> and IVF in most cases. Congratulations to all involved with this
>> project!
>
>
> Over the last decade and a half I have developed an 80,000 line
> environmental modeling utility library. All of it, including the
> Makefile system, work cleanly on AIX/XLF (with choice of underscoring
> convention), IRIX (5 and 6, "f77" or "f90"), Linux Alpha/DEC "fort",
> Linux IA64 (Intel, gcc/g77, gcc/g95), Linux x86 (gcc/g77, gcc/g95,
> Intel, PathScale, PGI (choice of underscoring), Sun StudioExpress, ...
|
| Show full article (2.44Kb) |
| no comments |
|
|
Author: DamianDamian Date: Sep 19, 2008 05:48
>> Since I can't report any new bugs, I'm glad to volunteer to work on
>> the things that excite me the most. I would be very excited to see
>> the following implemented and will contribute if someone can give me
>> specific guidance on where to start with these:
>> 1. allocatable scalars
>> 2. final procedures
>
> One of those Google SoC students mentioned elsewhere in this
> already undertook final procedures. The patch will appear in 4.5.
>
>> 3. polymorphic variables
>> 4. type guard statements
>> These are the most important things I need from gfortran to get it to ...
|
| Show full article (2.16Kb) |
| no comments |
|
|
Author: Carlie J. CoatsCarlie J. Coats Date: Sep 19, 2008 06:27
Arjen Markus wrote:
> On 19 sep, 14:15, "Carlie J. Coats" jyarborough.com> wrote:>> Al Greynolds wrote:
>>> Over the last few years I have developed a 30,000 line Fortran-95
>>> engineering application using simultaneously several compilers (XLF,
>>> LF95, G95, and IVF). During that time I toyed with Gfortran and put
>>> up with the 2 steps forward, 1 step back of each binary build.
>>> However, I'm now happy to report my "last" issue with it has been
>>> resolved and more importantly performance is almost identical to XLF
>>> and IVF in most cases. Congratulations to all involved with this
>>> project!
>>> Al Greynolds
>>> www.ruda.com>> Over the last decade and a half I have developed an 80,000 line
>> environmental modeling utility library. All of it, including the
>> Makefile system, work cleanly on AIX/XLF (with choice of underscoring
>> convention), IRIX (5 and 6, "f77" or "f90"), Linux Alpha/DEC "fort",
>> Linux IA64 (Intel, gcc/g77, gcc/g95), Linux x86 (gcc/g77, gcc/g95,
>> Intel, PathScale, PGI (choice of underscoring), Sun StudioExpress,
>> Absoft (choice of underscoring), OSF1/fort, SunOS (4 or 5, f77 or f90), ...
|
| Show full article (3.61Kb) |
| no comments |
|
|
Author: Arjen MarkusArjen Markus Date: Sep 19, 2008 06:48
On 19 sep, 15:27, "Carlie J. Coats" jyarborough.com> wrote:
I got it, I compiled the file bilin.f - no problem. Then
I compiled it with the option -openmp that I saw in your
compile statement ... and got the file "penmp" instead
of bilin.o !
I do not know if gfortran supports OpenMP, but at least the
flag -openmp seems to be interpreted as -o "penmp", setting
the output file.
Regards,
Arjen
|
| |
| no comments |
|
|
Author: Paul van DelstPaul van Delst Date: Sep 19, 2008 07:04
Arjen Markus wrote:
> On 19 sep, 15:27, "Carlie J. Coats" jyarborough.com> wrote:>
> I got it, I compiled the file bilin.f - no problem. Then
> I compiled it with the option -openmp that I saw in your
> compile statement ... and got the file "penmp" instead
> of bilin.o !
>
> I do not know if gfortran supports OpenMP, but at least the
> flag -openmp seems to be interpreted as -o "penmp", setting
> the output file.
Wow, good catch.
|
| Show full article (1.17Kb) |
| no comments |
|
|
|
|
|
Author: JayBeeJayBee Date: Sep 19, 2008 07:14
On 2008-09-19, Arjen Markus wrote:> On 19 sep, 15:27, "Carlie J. Coats" jyarborough.com> wrote:>
> I got it, I compiled the file bilin.f - no problem. Then
> I compiled it with the option -openmp that I saw in your
> compile statement ... and got the file "penmp" instead
> of bilin.o !
>
> I do not know if gfortran supports OpenMP, but at least the
> flag -openmp seems to be interpreted as -o "penmp", setting
> the output file.
|
| Show full article (0.96Kb) |
| no comments |
|
|
|
|
