All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: wyb@topsec.com.cn
Cc: macro@linux-mips.org, sskowron@ET.PUT.Poznan.PL.redhat.com,
	rsandifo@redhat.com, linux-mips@linux-mips.org
Subject: Re: unmatched R_MIPS_HI16/LO16 on gcc 3.4.3
Date: Mon, 24 Jul 2006 23:44:24 -0400	[thread overview]
Message-ID: <20060725034424.GB22138@linux-mips.org> (raw)
In-Reply-To: <004001c6af95$14585900$0100000a@codingman>

On Tue, Jul 25, 2006 at 10:49:56AM +0800, wyb@topsec.com.cn wrote:

> I met similar problem as Stanislaw Skowronek, but for gcc 3.4.3. I created a
> kernel module, when insmod, kernel reported "dangerous relocation". I traced
> the bug, found unmatched R_MIPS_HI16/LO16 in module's elf file, and kernel
> refused to relocate:
> ...
> 00015a5c  00039a05 R_MIPS_HI16       0000000c   tos_net_debug
> 00015a68  00000204 R_MIPS_26         00000000   .text
> 00015a64  00046005 R_MIPS_HI16       0006b598   arp_proxy_list
> 00015a6c  00046006 R_MIPS_LO16       0006b598   arp_proxy_list
> ...
> 
> My problem arised when expression on tos_net_debug could be optimized out,
> it seemed like gcc optimized out the LO16, but left HI16.
> 
> The original discussion on similar problem is at
> http://www.linux-mips.org/archives/linux-mips/2005-05/msg00097.html

Do you have a testcase, a kernel .config file to trigger this?

  Ralf

  reply	other threads:[~2006-07-25  3:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  2:49 unmatched R_MIPS_HI16/LO16 on gcc 3.4.3 wyb
2006-07-25  2:49 ` wyb
2006-07-25  3:44 ` Ralf Baechle [this message]
2006-07-31  1:58   ` wyb
2006-07-31  1:58     ` wyb
2006-07-31  8:34     ` Thiemo Seufer

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=20060725034424.GB22138@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=rsandifo@redhat.com \
    --cc=sskowron@ET.PUT.Poznan.PL.redhat.com \
    --cc=wyb@topsec.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.