public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51943] [OOP] ICE in conv_function_val
Date: Sun, 22 Jan 2012 19:00:00 -0000	[thread overview]
Message-ID: <bug-51943-4-sogay3EFA8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51943-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org
            Summary|the compile declares an     |[OOP] ICE in
                   |internal error when         |conv_function_val
                   |compiling  a fortran 2003   |
                   |source file                 |

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-22 17:54:11 UTC ---
I think this issue is a duplicate of PR 51870 - and of PR 48705. At least the
program works with a draft patch for those PRs.

Note that I had to comment the USE statement in the example and replace it by a
"logical :: debugging" line.


  parent reply	other threads:[~2012-01-22 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 16:43 [Bug fortran/51943] New: the compile declares an internal error when compiling a fortran 2003 source file dominique.pelletier at polymtl dot ca
2012-01-22 16:51 ` [Bug fortran/51943] " dominique.pelletier at polymtl dot ca
2012-01-22 17:51 ` kargl at gcc dot gnu.org
2012-01-22 19:00 ` burnus at gcc dot gnu.org [this message]
2012-01-27 10:12 ` [Bug fortran/51943] [OOP] ICE in conv_function_val pault at gcc dot gnu.org
2012-01-27 10:26 ` pault 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-51943-4-sogay3EFA8@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).