public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kristopher.kuhlman at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47601] [OOP] Internal Error: mio_component_ref(): Component not found Date: Wed, 08 Jun 2011 13:49:00 -0000 [thread overview] Message-ID: <bug-47601-4-7xtAduuqgO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47601-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47601 --- Comment #31 from Kris <kristopher.kuhlman at gmail dot com> 2011-06-08 13:49:21 UTC --- (In reply to comment #30) > (In reply to comment #29) > > Will this fix be applied to 4.6 or 4.5? > However, if your life depends on it, we could maybe consider having an > exception from that rule and doing a backport to the 4.6 branch (which is still > young), given that the patch is relatively small and simple. Although my *life* does not depend on it, I think backporting this fix to 4.6 would be beneficial, because it will be a while before 4.7 will be released and used widely. It seems to me that these sort of fixes are required before people will start using the more modern features of Fortran03/gfortran. Thanks for fixing this, regardless.
next prev parent reply other threads:[~2011-06-08 13:49 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-03 18:40 [Bug fortran/47601] New: Internal Error (mio_component_ref(): Component not found) with strange behavior townsend at astro dot wisc.edu 2011-02-03 18:45 ` [Bug fortran/47601] " townsend at astro dot wisc.edu 2011-02-03 18:59 ` mikael at gcc dot gnu.org 2011-02-03 19:20 ` townsend at astro dot wisc.edu 2011-02-03 19:31 ` mikael at gcc dot gnu.org 2011-02-03 21:17 ` townsend at astro dot wisc.edu 2011-02-03 21:54 ` mikael at gcc dot gnu.org 2011-02-03 22:13 ` dominiq at lps dot ens.fr 2011-02-03 23:13 ` [Bug fortran/47601] Internal Error: mio_component_ref(): Component not found janus at gcc dot gnu.org 2011-03-29 19:51 ` [Bug fortran/47601] [OOP] " janus at gcc dot gnu.org 2011-04-04 12:56 ` mikael at gcc dot gnu.org 2011-04-04 13:35 ` kristopher.kuhlman at gmail dot com 2011-05-26 18:15 ` townsend at astro dot wisc.edu 2011-05-26 21:43 ` janus at gcc dot gnu.org 2011-05-26 21:47 ` townsend at astro dot wisc.edu 2011-05-27 4:02 ` kristopher.kuhlman at gmail dot com 2011-05-28 12:49 ` burnus at gcc dot gnu.org 2011-05-28 14:19 ` janus at gcc dot gnu.org 2011-05-28 14:43 ` dominiq at lps dot ens.fr 2011-05-28 15:12 ` janus at gcc dot gnu.org 2011-05-28 15:21 ` burnus at gcc dot gnu.org 2011-05-28 15:49 ` janus at gcc dot gnu.org 2011-05-28 16:56 ` dominiq at lps dot ens.fr 2011-05-28 17:57 ` janus at gcc dot gnu.org 2011-05-28 21:21 ` dominiq at lps dot ens.fr 2011-05-29 13:15 ` janus at gcc dot gnu.org 2011-05-29 20:33 ` janus at gcc dot gnu.org 2011-05-29 21:02 ` janus at gcc dot gnu.org 2011-05-29 21:36 ` townsend at astro dot wisc.edu 2011-06-08 13:13 ` kristopher.kuhlman at gmail dot com 2011-06-08 13:40 ` janus at gcc dot gnu.org 2011-06-08 13:49 ` kristopher.kuhlman at gmail dot com [this message] 2011-06-19 21:07 ` janus at gcc dot gnu.org 2011-06-19 21:16 ` janus at gcc dot gnu.org 2011-06-19 21:19 ` townsend at astro dot wisc.edu 2011-06-20 2:32 ` kristopher.kuhlman at gmail dot com
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-47601-4-7xtAduuqgO@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: linkBe 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).