public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: davem@redhat.com
To: gcc-gnats@gcc.gnu.org
Cc: rth@redhat.com, jakub@redhat.com
Subject: target/6421: .hidden binutils bug craps up sparc builds
Date: Tue, 23 Apr 2002 06:46:00 -0000	[thread overview]
Message-ID: <20020423133631.23357.qmail@sources.redhat.com> (raw)


>Number:         6421
>Category:       target
>Synopsis:       .hidden binutils bug craps up sparc builds
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 23 06:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     davem@redhat.com
>Release:        unknown-1.0
>Organization:
>Environment:
GCC 3.1 CVS - sparc-linux
>Description:
Due to a bug in Sparc binutils, .hidden directives
can cause GOT entries to not be relocated.
The end result during builds is a mis-link of portions
of libgcc (in particular the &__bb_exit_func in
libgcc2.c is no relocated and has 0x0 as it's address).

It is fixed in binutils CVS, however at gcc-3.1 release
time there will be no public binutils release with the
fix.  We need to check in configure if the bug exists
or not, and if so act as if .hidden support is not present.
>How-To-Repeat:
Build on sparc target using binutils-2.12
>Fix:
Richard is working on configury bits to detect this
bug properly.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-23 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  6:46 davem [this message]
2002-04-23  6:50 davem
2002-04-24 18:33 rth
2002-04-26  5:00 davem

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=20020423133631.23357.qmail@sources.redhat.com \
    --to=davem@redhat.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rth@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).