public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Subject: fortran/6545: GOT page/offset relocation out of range building LAPACK
Date: Thu, 02 May 2002 20:46:00 -0000	[thread overview]
Message-ID: <20020503033634.17870.qmail@sources.redhat.com> (raw)


>Number:         6545
>Category:       fortran
>Synopsis:       GOT page/offset relocation out of range building LAPACK
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 02 20:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        gcc 3.1
>Organization:
>Environment:
mips-sgi-irix6.5
>Description:
Linking case xblat3z in LAPACK testsuite fails. 

This is a regression from 3.0 and 2.95.

/exd6/billingd/obj/gcc-3.1/gcc/g77 -B/exd6/billingd/obj/gcc-3.1/gcc/ -L/exd6/billingd/obj/gcc-3.1/mips-sgi-irix6.5/libf2c -L/exd6/billingd/obj/gcc-3.1/mips-sgi-irix6.5/libf2c -L/exd6/billingd/obj/gcc-3.1/mips-sgi-irix6.5/libf2c/.libs zblat3.o \
        ../../blas.a -o ../xblat3z
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18410.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x1841c.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18428.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18434.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18444.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18450.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x1845c.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18468.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18474.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18480.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18490.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18528.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x18534.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: ERROR 104: GOT page/offset relocation out of range: zblat3.o section: .rela.text relocation offset: 0x1854c.
Please use -LD_LAYOUT:lgot_buffer=20. If that doesn't work see the gp_overflow(5) manpage.
ld32: INFO 152: Output file removed because of error.

>How-To-Repeat:
Build and run LAPACK testsuite 
http://gcc.gnu.org/gcc-3.1/testing-lapack.html
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-03  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 20:46 David.Billinghurst [this message]
2002-05-06 12:50 rth
2002-05-06 12:56 rth
2002-05-08 23:46 Billinghurst, David (CRTS)
2002-08-22 14:56 Toon Moene
2002-10-24 12:06 Nathanael Nerode
2002-10-25 16:34 neroden

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=20020503033634.17870.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --cc=gcc-gnats@gcc.gnu.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).