From: John David Anglin <dave.anglin@bell.net>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Link error in CMake for HPPA1.1, wrong result for HPPA 2.0
Date: Wed, 7 Sep 2011 19:35:42 -0400 [thread overview]
Message-ID: <BLU0-SMTP85AE9387481754DD11D7CE971F0@phx.gbl> (raw)
In-Reply-To: <7292253.L43gRO36Hq@donald.sf-tec.de>
On 29-Aug-11, at 2:31 PM, Rolf Eike Beer wrote:
> You wrote:
>> On 8/29/2011 4:12 AM, Rolf Eike Beer wrote:
>
>>> Confirmed, it is a regression in gcc 4.5. If I build using 4.4.6
>>> everything works fine. I'll file a bug report tonight.
>>
>> Interesting, there's not much difference in the PA backend for
>> these two
>> versions.
>>
>> Add me (danglin at gcc.gnu.org) to the CC list on the GCC bug
>> report and
>> I'll try to
>> duplicate the problem.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50230
>
> Eike
The problem appears to be that comdat groups and stubs don't get along
with each other. Comdat groups seem to get merged and this can result
in out of range branches.
Linking with the --unique='.text.*' option avoids the error, but this
probably
breaks comdat and discard support.
For now, I think the best solution (untested) is to configure GCC with
the
--disable-comdat option.
I'm going to file a binutils PR.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2011-09-07 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 10:37 Link error in CMake for HPPA1.1, wrong result for HPPA 2.0 Rolf Eike Beer
2011-08-25 14:06 ` Carlos O'Donell
2011-08-25 15:21 ` Rolf Eike Beer
2011-08-25 15:46 ` John David Anglin
2011-08-29 8:12 ` Rolf Eike Beer
2011-08-29 9:47 ` Rolf Eike Beer
2011-08-29 14:38 ` John David Anglin
2011-08-29 18:31 ` Rolf Eike Beer
2011-09-07 23:35 ` John David Anglin [this message]
2011-09-08 15:22 ` Carlos O'Donell
2011-08-26 8:00 ` Rolf Eike Beer
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=BLU0-SMTP85AE9387481754DD11D7CE971F0@phx.gbl \
--to=dave.anglin@bell.net \
--cc=eike-kernel@sf-tec.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.