[Bug fortran/79382] DTIO ICE

walt.brainerd at gmail dot com gcc-bugzilla@gcc.gnu.org
Mon Feb 6 18:44:00 GMT 2017


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79382

--- Comment #6 from Walt Brainerd <walt.brainerd at gmail dot com> ---
You are probably right, but I have done all this on my home computer,
so I need to look at things again this evening. I do have ifort there and
will let you know.

I was trying all kinds of variations and can't remember what happened
with what. I did have one strange problem with ifort also (probably
related).

At least you have the ICE, which needs to be fixed somehow.

Thanks for your comments.

On Mon, Feb 6, 2017 at 11:01 AM, paul.richard.thomas at gmail dot com <
gcc-bugzilla@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79382
>
> --- Comment #5 from paul.richard.thomas at gmail dot com
> <paul.richard.thomas at gmail dot com> ---
> Hi Walt,
>
> My reading of the situation is that since, in this version, the
> generic procedure is typebound in a public derived type, the PUBLIC
> attribute is already accorded it..... I think!
>
> Do you have access to a recent copy of ifort? Mine is on my
> workstation, which is still in storage after a house move. I would be
> curious to know how it responds to both the typebound and the explicit
> generic interface versions.
>
> Best regards
>
> Paul
>
> On 6 February 2017 at 17:50, walt.brainerd at gmail dot com
> <gcc-bugzilla@gcc.gnu.org> wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79382
> >
> > --- Comment #4 from Walt Brainerd <walt.brainerd at gmail dot com> ---
> > Sorry, I forgot to remove the extraneous USE statement
> > which cutting down from the original code.
> >
> > I am not good with this new stuff; please explain what
> > the syntax error is? If the PUBLIC statement is not correct,
> > how do you make the write(formatted) interface public?
> >
> > Thanks for looking at this so quickly.
> >
> > --
> > You are receiving this mail because:
> > You are on the CC list for the bug.
>
> --
> You are receiving this mail because:
> You reported the bug.
>


More information about the Gcc-bugs mailing list