From: Paul Winalski <paul.winalski@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C entry keyword
Date: Tue, 30 Oct 2018 13:53:26 -0400 [thread overview]
Message-ID: <CABH=_VTyHe6cOUgR5ByPRq=kQOdH+EUrJgmo=nByLa_sA1XE_w@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfo+hXvkoGw1GnYoRAeBPHp-Ex6=PGhHLaDKu7AoKj3oew@mail.gmail.com>
In Fortran secondary entry points served two main purposes. It
allowed for sharing of code for similar routines (as in Angelo
Papenhoff's C example), which was important when your program had to
fit in only a few K of memory. Secondly, it provided partial relief
for Fortran's very restrictive variable-scoping rules.
It's a pain in the butt for compiler optimizers, although certain
modern interprocedural optimizations emit code that is the moral
equivalent of a routine with multiple entry points.
-Paul W.
prev parent reply other threads:[~2018-10-30 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 8:02 Steve Simon
2018-10-30 8:51 ` Lars Brinkhoff
2018-10-30 9:12 ` Angelo Papenhoff
2018-10-30 13:32 ` Paul Winalski
2018-10-30 13:56 ` Warner Losh
2018-10-30 17:53 ` Paul Winalski [this message]
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='CABH=_VTyHe6cOUgR5ByPRq=kQOdH+EUrJgmo=nByLa_sA1XE_w@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=imp@bsdimp.com \
--cc=tuhs@minnie.tuhs.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 NNTP newsgroup(s).