public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34545] ICE when compiling Fortran 95 code
Date: Wed, 02 Jan 2008 21:57:00 -0000 [thread overview]
Message-ID: <20080102215700.5df4KWjt4Qb_lBkK48DU72HgM-0ayQrsBXKBtwDbp3E@z> (raw)
In-Reply-To: <bug-34545-15536@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from pault at gcc dot gnu dot org 2008-01-02 21:00 -------
(In reply to comment #13)
> The patch in comment #12 works as advertised without regression in 32 and 64
> bit modes on ppc/Intel and my favourite platform.
>
Thanks for the test. I have been through several variants and think that this
is the most hygenic:
Index: gcc/fortran/module.c
===================================================================
*** gcc/fortran/module.c (revision 131237)
--- gcc/fortran/module.c (working copy)
*************** load_needed (pointer_info *p)
*** 3525,3530 ****
--- 3525,3536 ----
associate_integer_pointer (q, ns);
}
+ /* Use the module sym as 'proc_name' so that gfc_get_symbol_decl
+ doesn't go pear-shaped if the symbol is used. */
+ if (!ns->proc_name)
+ gfc_find_symbol (p->u.rsym.module, gfc_current_ns,
+ 1, &ns->proc_name);
+
sym = gfc_new_symbol (p->u.rsym.true_name, ns);
sym->module = gfc_get_string (p->u.rsym.module);
strcpy (sym->binding_label, p->u.rsym.binding_label);
I'm going to regtest in a few minutes but I'm confident that it's OK. It has
the advantage too that -fdump-parse-tree produces soemthing useful.
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34545
next prev parent reply other threads:[~2008-01-02 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 4:47 [Bug fortran/34545] New: " jon_d_r at msn dot com
2007-12-21 4:50 ` [Bug fortran/34545] " jon_d_r at msn dot com
2007-12-21 4:57 ` jon_d_r at msn dot com
2007-12-21 6:09 ` jv244 at cam dot ac dot uk
2007-12-21 6:14 ` kargl at gcc dot gnu dot org
2007-12-21 7:39 ` burnus at gcc dot gnu dot org
2007-12-21 9:47 ` dfranke at gcc dot gnu dot org
2007-12-21 12:28 ` pinskia at gcc dot gnu dot org
2007-12-26 18:36 ` jon_d_r at msn dot com
2007-12-26 22:07 ` kargl at gcc dot gnu dot org
2007-12-27 10:34 ` jon_d_r at msn dot com
2007-12-29 8:57 ` dfranke at gcc dot gnu dot org
2008-01-01 17:11 ` pault at gcc dot gnu dot org
2008-01-01 17:24 ` pault at gcc dot gnu dot org
2008-01-01 22:47 ` dominiq at lps dot ens dot fr
2008-01-02 21:57 ` pault at gcc dot gnu dot org [this message]
2008-01-06 19:36 ` burnus at gcc dot gnu dot org
2008-01-06 21:37 ` paulthomas2 at wanadoo dot fr
2008-01-06 22:15 ` pault at gcc dot gnu dot org
2008-01-07 10:05 ` pault at gcc dot gnu dot 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=20080102215700.5df4KWjt4Qb_lBkK48DU72HgM-0ayQrsBXKBtwDbp3E@z \
--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).