From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Subject: Re: weak and strong aliases for global data fail
Date: Tue, 23 May 2006 10:29:00 -0000 [thread overview]
Message-ID: <200605220031.51867.vapier@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0605171313440.16172-400000@lnx.bridge.intra>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Wednesday 17 May 2006 07:19, Peter S. Mazinger wrote:
> Attached tests show a case, when a final binary is OK if
> compiled w/ -fPIC (or -fPIE, it does not have to be ET_DYN, but can be),
> else it fails if using aliases (both weak and strong) for global data.
>
> Sorry for the "big" test cases, I couldn't make them smaller.
this is related to this thread on the glibc list:
http://sourceware.org/ml/libc-alpha/2006-04/msg00044.html
http://sourceware.org/ml/libc-alpha/2006-04/msg00048.html
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-05-23 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 17:02 Peter S. Mazinger
2006-05-23 0:12 ` Peter S. Mazinger
2006-05-23 9:35 ` Alan Modra
2006-05-24 15:06 ` Peter S. Mazinger
2006-05-24 17:05 ` Alan Modra
2006-05-23 10:29 ` Mike Frysinger [this message]
2006-05-24 15:34 ` Peter S. Mazinger
2006-05-26 2:44 ` Mike Frysinger
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=200605220031.51867.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.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).