From: Richard Henderson <rth@redhat.com>
To: Per Bothner <per@bothner.com>
Cc: Geoff Keating <geoffk@redhat.com>, gcc@gcc.gnu.org
Subject: Re: misleading statement in bugs.html#known
Date: Thu, 06 Dec 2001 15:48:00 -0000 [thread overview]
Message-ID: <20011206154106.A9641@redhat.com> (raw)
In-Reply-To: <3C0FD1BF.6000709@bothner.com>; from per@bothner.com on Thu, Dec 06, 2001 at 12:14:55PM -0800
On Thu, Dec 06, 2001 at 12:14:55PM -0800, Per Bothner wrote:
> 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.
The "better way" is defaulting to PIC for any symbol not known
to be defined locally. We do this on Alpha and IA-64. It's not
really practical to do the same for x86 though. :-/
r~
next prev parent reply other threads:[~2001-12-06 23:41 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
2001-12-06 15:48 ` Richard Henderson [this message]
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=20011206154106.A9641@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@redhat.com \
--cc=per@bothner.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).