From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ld failure
Date: Tue, 02 May 2000 22:32:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205069@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205047@msgid-missing>
/usr/bin/ld: dw: __gp does not cover short data segment
Sorry, I forgot to answer this.
Something is still broken. I don't know what. There are a few ways that you
could get here.
1) You have a program with millions of small static scalar variables. If so,
try using -mno-sdata, or rewrite your program.
2) You are explicitly allocating variables to the short data segment, either
by using attribute section, or by using a special linker script, or by
writing assembly language code that puts data in the short data segement.
If so, you need to fix your code to stop putting so much data in the short
data segment.
3) There is a linker bug, that is causing the out-of-range call support to
fail in a way that makes it look like the short data segment is too big.
#3 seems like the most likely explanation. We would need a complete testcase
to reproduce this, which means a copy of all object files and libraries that
you are linking together, together with the linker command line. Fixing this
would be a low priority, so it may be a few weeks before it gets fixed.
Jim
next prev parent reply other threads:[~2000-05-02 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 14:09 [Linux-ia64] ld failure Christoph Rohland
2000-04-26 18:58 ` Jim Wilson
2000-04-26 20:58 ` Saxena, Sunil
2000-04-27 17:39 ` Christoph Rohland
2000-05-02 22:32 ` Jim Wilson [this message]
2000-05-03 7:33 ` Christoph Rohland
2000-05-09 16:52 ` Christoph Rohland
2000-05-09 17:36 ` Uros Prestor
2000-05-09 17:56 ` Christoph Rohland
2000-05-24 9:52 ` Christoph Rohland
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=marc-linux-ia64-105590678205069@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@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