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/47082] [OOP] ICE in gfc_conv_component_ref
Date: Wed, 29 Dec 2010 15:59:00 -0000 [thread overview]
Message-ID: <bug-47082-4-eH0M6I18gh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47082-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47082
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.12.29 15:58:51
Ever Confirmed|0 |1
--- Comment #2 from janus at gcc dot gnu.org 2010-12-29 15:58:51 UTC ---
I have stared at this problem for a while now, but I'm still puzzled about its
origin. All I could come up with is this ad-hoc patch:
Index: gcc/fortran/trans-expr.c
===================================================================
--- gcc/fortran/trans-expr.c (revision 168301)
+++ gcc/fortran/trans-expr.c (working copy)
@@ -6085,6 +6085,7 @@ gfc_trans_class_init_assign (gfc_code *code)
rhs = gfc_copy_expr (code->expr1);
gfc_add_vptr_component (rhs);
+ gfc_get_derived_type (rhs->ts.u.derived);
gfc_add_def_init_component (rhs);
sz = gfc_copy_expr (code->expr1);
This does not solve the problem fully, but it reduces it to PR46448:
/tmp/cc9UG1CN.s: Assembler messages:
/tmp/cc9UG1CN.s:65: Error: symbol `__copy_m0_t0_' is already defined
next prev parent reply other threads:[~2010-12-29 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 20:00 [Bug fortran/47082] New: " sfilippone at uniroma2 dot it
2010-12-28 21:05 ` [Bug fortran/47082] " janus at gcc dot gnu.org
2010-12-29 15:59 ` janus at gcc dot gnu.org [this message]
2011-01-04 13:28 ` janus at gcc dot gnu.org
2011-01-04 13:31 ` [Bug fortran/47082] [4.6 Regression] " janus at gcc dot gnu.org
2011-01-14 14:24 ` rguenth at gcc dot gnu.org
2011-01-17 19:03 ` jakub at gcc dot gnu.org
2011-02-01 10:00 ` pault at gcc dot gnu.org
2011-02-01 22:32 ` pault at gcc dot gnu.org
2011-02-02 19:51 ` pault at gcc dot gnu.org
2011-02-02 19:52 ` 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-47082-4-eH0M6I18gh@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).