public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43366] [OOP][F2008] Intrinsic assign to polymorphic variable
Date: Fri, 04 Feb 2011 09:32:00 -0000 [thread overview]
Message-ID: <bug-43366-4-geQVZNC5qQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43366-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43366
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> 2011-02-04 09:32:01 UTC ---
(In reply to comment #5)
> Realloc-on-assign for scalars was implemented in r169356.
>
> Paul, what does it take to make this work for polymorphic scalars?
Not a lot, I think. If you take a look in gfc_trans_allocate, there is a bit
that I think that you must have written, which initialises CLASS variables. I
would have thought that this can be lifted and deposited wholesale in
trans_assignment1 and gfc_trans_allocate reconfigured to use the assignement.
I am taking a look at gfc_trans_allocate this lunchtime; there's something not
quite right structurally with it. I attempted to add a patch of code to have a
single evaluation of the SOURCE expression and wound up displacing unrelated
declarations, when I added the se.post to the end of the main block. gimple did
not like it at all :-( I'll come back to you.
Cheers
Paul
next prev parent reply other threads:[~2011-02-04 9:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43366-4@http.gcc.gnu.org/bugzilla/>
2011-02-03 20:45 ` janus at gcc dot gnu.org
2011-02-03 20:56 ` janus at gcc dot gnu.org
2011-02-03 21:05 ` janus at gcc dot gnu.org
2011-02-03 21:26 ` burnus at gcc dot gnu.org
2011-02-03 21:28 ` burnus at gcc dot gnu.org
2011-02-03 21:29 ` burnus at gcc dot gnu.org
2011-02-04 9:32 ` pault at gcc dot gnu.org [this message]
2011-02-10 22:43 ` janus at gcc dot gnu.org
2011-02-11 0:27 ` janus at gcc dot gnu.org
2011-02-11 19:43 ` burnus at gcc dot gnu.org
2011-07-22 12:09 ` burnus at gcc dot gnu.org
2012-01-06 10:25 ` burnus at gcc dot gnu.org
2012-02-09 17:52 ` burnus at gcc dot gnu.org
2012-04-10 21:06 ` abenson at caltech dot edu
2013-08-08 14:36 ` [Bug fortran/43366] [OOP][F08] " janus at gcc dot gnu.org
2013-09-18 18:15 ` burnus at gcc dot gnu.org
2010-03-14 14:00 [Bug fortran/43366] New: [OOP][F2008] " burnus at gcc dot gnu dot org
2010-03-14 14:01 ` [Bug fortran/43366] " burnus at gcc dot gnu dot org
2010-08-03 11:23 ` janus 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=bug-43366-4-geQVZNC5qQ@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).