This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/14959] [gfortran] not recognizing internal file in PURE/ELEMENATAL function
- From: "jtk at octopus dot scif dot ou dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 May 2004 00:27:55 -0000
- Subject: [Bug fortran/14959] [gfortran] not recognizing internal file in PURE/ELEMENATAL function
- References: <20040414220813.14959.jtk@ou.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jtk at octopus dot scif dot ou dot edu 2004-05-13 00:27 -------
Subject: Re: [gfortran] not recognizing internal file in PURE/ELEMENATAL function
Hello,
The newest copy of g95 now makes it past this problem. I now have other
problems that I will need to narrow down before submitting a bug report.
I do apologize for leaving in the dependency. We use quite a few nested
modules, and many F90/95 features. In fact, the sun compilers didn't
even generate anything except a divide by zero error compiling our code.
SGI and the Intel version 8 compilers also don't make it without
internal compiler errors. Intel v7 and Compaq Digital Fortran do make
it. All in all, it looks like the development is going quite nicely.
As a side note, what exactly is the difference between the gfortran and
g95 projects? The home page for G95 points to the gfortran bugzilla
page.
Thanks,
Tim Kwiatkowski
On Wed, May 12, 2004 at 11:01:07PM +0000, tobi at gcc dot gnu dot org wrote:
>
> ------- Additional Comments From tobi at gcc dot gnu dot org 2004-05-12 23:01 -------
> (In reply to comment #3)
> > Can you provide a self contained example?
> No, because I can't reproduce it. The testcase I gave removes the dependency on
> the module, but it doesn't fail. Looking at the original bug submission again,
> this seems to be a problem in g95, not gfortran.
>
> J. Timothy, if your problem persists, and if I understand correctly that your
> problem is in g95, I suggest you ask Andy Vaught about it (and suggest to him
> that he works with the gfortran people again :-). According to their status
> page, it's fixed there as well.
>
> Independent of that, we would also appreciate if you tried gfortran on your
> code, and tell us if it works.
>
> I'm closing this bug as WORKSFORME. If you believe that you did actually find a
> bug in gfortran, you're welcome to open it again. If you do so, please provide
> more detailed information.
>
> --
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |tobi at gcc dot gnu dot org
> Status|WAITING |RESOLVED
> Resolution| |WORKSFORME
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14959
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14959