public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42274] [fortran-dev Regression] ICE: segmentation fault
Date: Sat, 05 Dec 2009 15:14:00 -0000 [thread overview]
Message-ID: <20091205151425.31476.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42274-9410@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from janus at gcc dot gnu dot org 2009-12-05 15:14 -------
(In reply to comment #8)
> With the patch in comment #7 the tests in pr41829 and the following ones
> segfault at runtime.
Since these run fine with a clean fortran-dev, this is a regression of my
patch, more exactly of the following part:
Index: gcc/fortran/symbol.c
===================================================================
--- gcc/fortran/symbol.c (revision 154956)
+++ gcc/fortran/symbol.c (working copy)
@@ -4751,6 +4751,7 @@ add_proc_component (gfc_component *c, gfc_symbol *
if (!c->tb)
c->tb = XCNEW (gfc_typebound_proc);
*c->tb = *st->n.tb;
+ c->tb->ppc = 1;
c->attr.procedure = 1;
c->attr.proc_pointer = 1;
c->attr.flavor = FL_PROCEDURE;
However, I fail to see why. Paul, do you have an idea?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42274
next prev parent reply other threads:[~2009-12-05 15:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 14:30 [Bug fortran/42274] New: " sfilippone at uniroma2 dot it
2009-12-04 14:31 ` [Bug fortran/42274] " sfilippone at uniroma2 dot it
2009-12-04 14:48 ` rguenth at gcc dot gnu dot org
2009-12-04 14:58 ` dominiq at lps dot ens dot fr
2009-12-04 15:02 ` sfilippone at uniroma2 dot it
2009-12-04 15:57 ` [Bug fortran/42274] [fortran-dev Regression] " burnus at gcc dot gnu dot org
2009-12-04 17:06 ` janus at gcc dot gnu dot org
2009-12-04 19:44 ` janus at gcc dot gnu dot org
2009-12-04 21:38 ` dominiq at lps dot ens dot fr
2009-12-05 11:21 ` janus at gcc dot gnu dot org
2009-12-05 13:31 ` dominiq at lps dot ens dot fr
2009-12-05 15:14 ` janus at gcc dot gnu dot org [this message]
2009-12-05 16:41 ` dominiq at lps dot ens dot fr
2009-12-06 13:33 ` pault at gcc dot gnu dot org
2009-12-10 21:21 ` janus at gcc dot gnu dot org
2010-03-02 9:47 ` dominiq at lps dot ens dot fr
2010-04-22 20:59 ` janus at gcc dot gnu dot org
2010-04-25 14:32 ` janus at gcc dot gnu dot org
2010-04-25 14:43 ` janus at gcc dot gnu dot org
2010-04-25 14:57 ` janus at gcc dot gnu dot org
2010-04-25 16:27 ` pault at gcc dot gnu dot org
2010-04-25 16:39 ` dominiq at lps dot ens dot fr
2010-04-25 16:43 ` janus at gcc dot gnu dot org
2010-04-25 17:10 ` janus at gcc dot gnu dot org
2010-04-25 17:16 ` janus at gcc dot gnu dot org
2010-04-25 18:24 ` janus at gcc dot gnu dot org
2010-04-25 18:28 ` paul dot richard dot thomas at gmail dot com
2010-04-25 18:59 ` paul dot richard dot thomas at gmail dot com
2010-04-25 19:17 ` sfilippone at uniroma2 dot it
2010-04-25 19:50 ` janus at gcc dot gnu dot org
2010-04-25 20:17 ` janus at gcc dot gnu dot org
2010-04-25 20:20 ` sfilippone at uniroma2 dot it
2010-04-25 21:44 ` janus at gcc dot gnu dot org
2010-04-25 22:26 ` janus at gcc dot gnu dot org
2010-04-26 8:23 ` dominiq at lps dot ens dot fr
2010-04-26 9:08 ` janus at gcc dot gnu dot org
2010-04-26 10:57 ` pault at gcc dot gnu dot org
2010-04-29 19:12 ` 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=20091205151425.31476.qmail@sourceware.org \
--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).