From: Per Bothner <per@bothner.com>
To: Geoff Keating <geoffk@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: misleading statement in bugs.html#known
Date: Thu, 06 Dec 2001 12:33:00 -0000 [thread overview]
Message-ID: <3C0FD1BF.6000709@bothner.com> (raw)
In-Reply-To: <jmitblz67i.fsf@geoffk.org>
Geoff Keating wrote:
> printf (&__stdin, ...)
>
> then this works with dynamic linking by creating space in the
> executable for '__stdin', resolving the address of __stdin at link
> time, and copying at startup time the initial contents of __stdin to
> that space
Ugh. Ick. This is unfortunate mechanism, not that I know enough
about dynamic linking to know if there is (or could be) a better
way. But it seems we're stuck with it.
Thanks for the replies and explanations.
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/
next prev parent reply other threads:[~2001-12-06 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 13:16 Per Bothner
2001-12-05 13:52 ` Geoff Keating
2001-12-06 12:33 ` Per Bothner [this message]
2001-12-06 15:48 ` Richard Henderson
2001-12-05 14:38 ` Andreas Schwab
2001-12-06 4:31 ` Gerald Pfeifer
2001-12-06 4:46 ` Andreas Schwab
2001-12-06 7:18 ` Gerald Pfeifer
2001-12-06 7:35 ` Andreas Schwab
2001-12-06 10:08 ` Gerald Pfeifer
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=3C0FD1BF.6000709@bothner.com \
--to=per@bothner.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@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).