public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nagl46 at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52111] [OOP] procedure pointer with polymorphic passed dummy argument
Date: Sat, 04 Feb 2012 11:03:00 -0000	[thread overview]
Message-ID: <bug-52111-4-LljfRSHsuN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52111-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52111

--- Comment #4 from alexander tismer <nagl46 at web dot de> 2012-02-04 11:02:55 UTC ---
I think you are right. Thanks again for your helpful annotations.

But I'm not sure if I understand everything correctly.

>> Thus, the compiler is not required to diagnose it - and, seemingly, 
>> the Cray compiler doesn't.

I think I understand this statement. And if I change my code like this:

>>  type(solver_t), target :: solverTarget
>>  integer :: val
>>  class(solverAbstract_t), pointer :: solver
>>
>>  solver => solverTarget
>>
>>  call solver%setPrec('l')
>>  call solver%solve(val)

Then I think program should fail because solveLeft_sub is called with
class(solverAbstract_t) as passed dummy argument. This is not conform with the
subroutine. 
In any case gfortran is right, but compiling my new program with Cray there is
no error. And as you mentionend this is ok, because argument checking is not
necessary. But is it correct that program execution is not stopped by an error?
In my opinion at runtime there is the above mentioned problem.


  parent reply	other threads:[~2012-02-04 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 16:21 [Bug fortran/52111] New: " nagl46 at web dot de
2012-02-03 16:22 ` [Bug fortran/52111] " nagl46 at web dot de
2012-02-03 17:32 ` burnus at gcc dot gnu.org
2012-02-03 17:52 ` nagl46 at web dot de
2012-02-04 11:03 ` nagl46 at web dot de [this message]
2012-02-05 16:43 ` burnus at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52111-4-LljfRSHsuN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).