public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47546] Internal error - free_pi_tree(): Unresolved fixup
Date: Wed, 02 Feb 2011 14:49:00 -0000	[thread overview]
Message-ID: <bug-47546-4-jIn8Qn3sxl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47546-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from janus at gcc dot gnu.org 2011-02-02 14:49:16 UTC ---
(In reply to comment #1)
> If gfortran is 4.5, I get 
> 
> hydro_fluxes.f90:7.18:
> 
>   use hydro_speeds
>                   1
> Internal Error at (1):
> mio_component_ref(): Component not found


I get the same error with gfortran 4.5, but 4.6 works nicely for me at r169520.
Rich, which version are you using?


  parent reply	other threads:[~2011-02-02 14:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 21:53 [Bug fortran/47546] New: " townsend at astro dot wisc.edu
2011-01-30 22:02 ` [Bug fortran/47546] " dominiq at lps dot ens.fr
2011-01-30 22:07 ` mikael at gcc dot gnu.org
2011-02-02 14:49 ` janus at gcc dot gnu.org [this message]
2011-02-02 16:53 ` townsend at astro dot wisc.edu
2011-02-02 17:15 ` janus at gcc dot gnu.org
2011-02-02 18:31 ` janus at gcc dot gnu.org
2011-02-02 18:51 ` dominiq at lps dot ens.fr
2011-02-02 19:31 ` janus at gcc dot gnu.org
2011-02-02 19:56 ` townsend at astro dot wisc.edu
2011-02-02 20:15 ` janus at gcc dot gnu.org
2011-02-02 21:04 ` dominiq at lps dot ens.fr
2011-02-02 21:17 ` janus at gcc dot gnu.org
2011-02-02 21:27 ` mikael at gcc dot gnu.org
2011-02-02 22:25 ` mikael at gcc dot gnu.org
2011-02-03  0:11 ` townsend at astro dot wisc.edu
2011-02-03 18:32 ` mikael at gcc dot gnu.org
2011-02-03 22:54 ` townsend at astro dot wisc.edu
2011-02-03 23:04 ` townsend at astro dot wisc.edu
2011-03-16  2:48 ` [Bug fortran/47546] [OOP] " townsend at astro dot wisc.edu
2011-03-16  2:50 ` jvdelisle at gcc dot gnu.org
2011-03-16  2:59 ` jvdelisle at gcc dot gnu.org
2011-03-16  3:01 ` jvdelisle at gcc dot gnu.org
2011-03-16  3:12 ` jvdelisle at gcc dot gnu.org
2011-03-16  4:45 ` jvdelisle at gcc dot gnu.org
2011-03-29 17:13 ` dominiq at lps dot ens.fr
2011-03-29 17:24 ` janus at gcc dot gnu.org
2011-03-29 17:37 ` janus at gcc dot gnu.org
2011-03-29 20:11 ` janus 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-47546-4-jIn8Qn3sxl@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).