From: "Carlos O'Donell" <carlos@systemhalted.org>
To: John David Anglin <dave.anglin@bell.net>
Cc: linux-parisc <linux-parisc@vger.kernel.org>, libc-ports@sourceware.org
Subject: Re: hppa: glibc and gcc 4.6, "error: _rtld_global_ro causes a section type conflict"
Date: Wed, 25 Apr 2012 04:06:00 -0000 [thread overview]
Message-ID: <CADZpyizS_HE4YLvw=ssi2Wi33q_c8L0MRECaUjhC7kKMtg6baQ@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP9C263F5C55BC27550263497260@phx.gbl>
On Tue, Apr 24, 2012 at 7:55 PM, John David Anglin <dave.anglin@bell.net> wrote:
> On 15-Apr-12, at 11:00 AM, Carlos O'Donell wrote:
>
>> When compiling glibc on magnum with gcc-4.6 I get an odd failure about
>> section type conflicts.
>
>
>
> After discussing the issue with Jakub Jelinek, it appears the bug is caused
> by placing
> function labels (plabels) in the constant pool.
Interesting.
> PA has done this for longer
> than I can
> remember, but it doesn't appear necessary. As you know, only ia64 and pa
> use plabels.
Yes, we both rely on the plabel code in glibc.
> This causes the setting of default flags for .data.rel.ro which conflict
> with those needed
> for _rtld_global_ro in the dynamic linker. The problem doesn't have
> anything directly
> to do with the handling of the variable _rtld_global_ro. This was what was
> confusing
> me as everything seemed generic.
Me too.
> I am testing a fix. Your testcase compiles successfully with the fix.
Excellent!
> The issue is incredibly subtle. I would guess it was just a matter of luck
> that other targets
> aren't affected given that the code in rtld.c is not exactly exactly kosher
> from GCC POV.
The dynamic linker isn't exactly kosher :-)
Cheers,
Carlos.
prev parent reply other threads:[~2012-04-25 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 15:00 Carlos O'Donell
2012-04-24 23:55 ` John David Anglin
2012-04-25 4:06 ` Carlos O'Donell [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='CADZpyizS_HE4YLvw=ssi2Wi33q_c8L0MRECaUjhC7kKMtg6baQ@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=dave.anglin@bell.net \
--cc=libc-ports@sourceware.org \
--cc=linux-parisc@vger.kernel.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).