From: Segher Boessenkool <segher@kernel.crashing.org>
To: Simon Vallet <linux-ppc@castalie.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: R_PPC_ADDR16_HI relocs in PPC modules ?
Date: Tue, 2 Jan 2007 21:48:31 +0100 [thread overview]
Message-ID: <0e6a409d0ffedd23495d2aed672632dd@kernel.crashing.org> (raw)
In-Reply-To: <20070102190944.70c19799@mlejnas.priv.castalie.org>
> Sure. As an example, here is some output of otool -rV and the
> corresponding
> disassembled text section part
>
> Relocation information (__TEXT,__text) 61126 entries
> address pcrel length extern type scattered symbolnum/value
> 00000654 False long False LO16 False 1 (__TEXT,__text)
> False long False PAIR False half = 0x0000
> 00000650 False long False HI16 False 1 (__TEXT,__text)
> False long False PAIR False half = 0x83fc
>
> 00000650 lis r12,hi16(_msw_report_event)
> 00000654 ori r12,r12,lo16(_msw_report_event)
Ah. lis and ori. HI16 is just fine there -- but note that
that doesn't use an add insn. You're patching the function
"apply_relocate_add()", so I guess some more work is needed?
Segher
next prev parent reply other threads:[~2007-01-02 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 16:25 R_PPC_ADDR16_HI relocs in PPC modules ? Simon Vallet
2007-01-02 17:16 ` Segher Boessenkool
2007-01-02 18:09 ` Simon Vallet
2007-01-02 20:48 ` Segher Boessenkool [this message]
2007-01-03 0:47 ` Paul Mackerras
2007-01-03 1:20 ` Segher Boessenkool
2007-01-02 20:41 ` Benjamin Herrenschmidt
2007-01-03 7:01 ` Simon Vallet
2007-01-03 9:58 ` Benjamin Herrenschmidt
2007-01-03 10:32 ` Simon Vallet
2007-01-03 20:36 ` Benjamin Herrenschmidt
2007-01-02 21:31 ` Alan Modra
2007-01-03 6:49 ` [PATCH] Add support for R_PPC_ADDR16_HI relocations Simon Vallet
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=0e6a409d0ffedd23495d2aed672632dd@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-ppc@castalie.org \
--cc=linuxppc-dev@ozlabs.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 NNTP newsgroup(s).