public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Jack Carter <Jack.Carter@imgtec.com>
Cc: Richard Sandiford <rdsandiford@googlemail.com>,
	"H.J. Lu" <hjl.tools@gmail.com>,
		"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: [MIPS] Is it legal for the assembler to generate more than 64K sections?
Date: Mon, 03 Feb 2014 21:37:00 -0000	[thread overview]
Message-ID: <CA+=Sn1kKJjB8ACEF4phpwXW4zMTj7jXfH4+SW770v=np+xHKWw@mail.gmail.com> (raw)
In-Reply-To: <4CEFBC1BE64A8048869F799EF2D2EEEE4C6F2BA0@BADAG02.ba.imgtec.org>

On Mon, Feb 3, 2014 at 1:12 PM, Jack Carter <Jack.Carter@imgtec.com> wrote:
>>(.text._ZN4llvm25SmallVectorTemplateCommonIN5clang19RecursiveASTVisitorINS1_11AttrVisitorEE10EnqueueJobEvE4backEv[_ZN4llvm25SmallVectorTemplateCommonIN5clang19RecursiveASTVisitorINS1_11AttrVisitorEE10EnqueueJobEvE4backEv]+0x64):
>>> relocation truncated to fit: R_MIPS_GOT16 against `no symbol'
>>>
>>> Basically building LLVM with a MIPS GCC. I noticed that the section
>>> count was way above 16 bits and seized on that as being the culprit.
>>
>>Ah, OK.  Looks like a multigot failure at face value.  Are you using
>>recent binutils (2.24)?  It has some fixes in that area.
>
> I rebased on Thursday.
>
> Multigot is a good area for me to look since I am mucking with the got with ifunc anyway.


It could also be that the GOT for that object file is just too big.  I
bet that is the case which means you need to use the option -mxgot .
Multigot only works with different object files, it does not work
inside one object file as far as I know.

Thanks,
Andrew Pinski

>
> Cheers,
>
> Jack
>
>>
>>Thanks,
>>Richard
>

      reply	other threads:[~2014-02-03 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 23:23 Jack Carter
2014-02-01  0:25 ` H.J. Lu
2014-02-03 18:13   ` Jack Carter
2014-02-03 20:29     ` Richard Sandiford
2014-02-03 20:51       ` Jack Carter
2014-02-03 20:59         ` Richard Sandiford
2014-02-03 21:12           ` Jack Carter
2014-02-03 21:37             ` Andrew Pinski [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='CA+=Sn1kKJjB8ACEF4phpwXW4zMTj7jXfH4+SW770v=np+xHKWw@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=Jack.Carter@imgtec.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=rdsandiford@googlemail.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).