From: "Thomas König" <tk@tkoenig.net>
To: gcc@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: Function pointers to a nested function / contained procedure
Date: Wed, 27 Mar 2019 07:48:00 -0000 [thread overview]
Message-ID: <0D3ECD50-9BC6-449F-A88D-948164AD60CA@tkoenig.net> (raw)
Hi Eric,
> There is an entire machinery in the middle-end and the back-ends to support this (look for trampolines/descriptors in the manual and the source code). This should essentially work out of the box for any language front-end.
Thanks for the pointer. The documentation I have seen seems to point out what to do in a back end to implement this, less towards what to do in a front end. And the source is big :-)
Could somebody maybe shed some additional light on what magic I would have to invoke in the Fortran front end?
Regards, Thomas
next reply other threads:[~2019-03-27 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 7:48 Thomas König [this message]
2019-03-27 9:02 ` Richard Biener
2019-03-27 9:09 ` Jakub Jelinek
2019-03-27 9:26 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 21:55 Thomas Koenig
2019-03-26 22:25 ` Eric Botcazou
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=0D3ECD50-9BC6-449F-A88D-948164AD60CA@tkoenig.net \
--to=tk@tkoenig.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc@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).