From: "Janus Weil" <jaydub66@googlemail.com>
To: "Paul Richard Thomas" <paul.richard.thomas@gmail.com>
Cc: "Fortran List" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 36322/36463
Date: Fri, 24 Oct 2008 13:01:00 -0000 [thread overview]
Message-ID: <854832d40810240509lfb8b436p4f9431ae051bffcb@mail.gmail.com> (raw)
In-Reply-To: <339c37f20810240424i2a974b7bvaa07dd112053f7fe@mail.gmail.com>
Hi Paul,
> I have a question, though: Is this patch not substantially
> duplicating the interface mapping that goes on in trans-expr.c?(This
> only occurred to me a few minutes ago)
Good question. Actually I was not aware of that mapping code,
therefore it may well be that there is some duplication in my patch
(theoretically).
OTOH, if I understand correctly, the code that you are referring to is
used to map the actual args to the formal args in a function call,
which is of course not what I need to do with my patch, though there
might be similarities.
What one needs to do for "PROCEDURE(i) :: p" is to make a complete
copy of the interface i, including all the formal arguments etc. So it
involves not so much a mapping, as merely a duplication of an
interface, which seems to be quite a difference to me.
But obviously I am not familiar with the mapping code, and so I might
be completely wrong. Maybe there is indeed the possibility to exploit
some of the mapping code for the patch. If you have an idea on how
that could work please let me know. I will try to investigate this.
Cheers,
Janus
next prev parent reply other threads:[~2008-10-24 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 11:04 Janus Weil
2008-10-24 12:23 ` Paul Richard Thomas
2008-10-24 13:01 ` Janus Weil [this message]
2008-10-27 14:37 ` Janus Weil
2008-10-27 14:44 ` Janus Weil
2008-10-31 20:08 ` Janus Weil
2008-10-31 20:18 ` Paul Richard Thomas
2008-11-01 13:28 ` Janus Weil
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=854832d40810240509lfb8b436p4f9431ae051bffcb@mail.gmail.com \
--to=jaydub66@googlemail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).