public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joerg Albert <jal2@gmx.de>
To: gcc-help@gcc.gnu.org
Subject: Re: gcc 4.8.1, powerpc, .data.rel.ro.local entry with no corresponding .fixup entry
Date: Mon, 10 Feb 2014 14:33:00 -0000	[thread overview]
Message-ID: <loom.20140210T151017-245@post.gmane.org> (raw)
In-Reply-To: <loom.20140203T154631-645@post.gmane.org>

Hi,

switched to gcc 4.8.2, but the problem remains.

It seems like .data.rel.ro.local contains pointers only
and its entries are not covered by any entries in .fixup.
All other .data.rel.ro.* sections contain arbitrary data -
if there are any pointers, there is always a corresponding
entry in .fixup.

Therefore I put .data.rel.ro.local between .got2 and .got in the
linker script file:

    KEEP(*(.got2))
    KEEP(*(.data.rel.ro.local))
    KEEP(*(.got))

which seems to solve the problem.

Is the above assumption valid? Or may it break with some other code
or with the next compiler version? It's quite hard to find documentation
about the usage of .data.rel.ro.local.

Thanks,
Joerg

      reply	other threads:[~2014-02-10 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 15:10 Joerg Albert
2014-02-10 14:33 ` Joerg Albert [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=loom.20140210T151017-245@post.gmane.org \
    --to=jal2@gmx.de \
    --cc=gcc-help@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).