From: matthew green <mrg@cygnus.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: re: elf-loader - accessor naming alternative
Date: Sat, 13 Jan 2001 16:05:00 -0000 [thread overview]
Message-ID: <16531.979430673@cygnus.com> (raw)
In-Reply-To: <20010113133802.D10767@redhat.com>
Somewhat to contradict my last suggestion regarding the accessor names
of the new elf64-capable loader, consider extending the loader so that
it can decide whether each incoming program section is code or data,
and direct the contents via the appropriate accessor.
actually, it already uses the insn accessor if the (program) header
flags indicate read & execute perms.
.mrg.
prev parent reply other threads:[~2001-01-13 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 10:38 Frank Ch. Eigler
2001-01-13 16:05 ` matthew green [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=16531.979430673@cygnus.com \
--to=mrg@cygnus.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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).