public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* HI16 / LO16 relocations.
@ 1999-08-03 15:10 Ralf Baechle
  1999-08-03 15:40 ` Mark Mitchell
  0 siblings, 1 reply; 3+ messages in thread
From: Ralf Baechle @ 1999-08-03 15:10 UTC (permalink / raw)
  To: Mark Mitchell, binutils, linux, linux-mips, linux-mips

Mark, for now I'm just posting this in the hope it may ring a bell.
It seems like HI16 / LO16 relocation pairs are not handled correctly
This may result in ``la $reg, symbol'' ending up after the final link
as ``la $reg, symbol + 0x10000''.

I'll try to come up with a resonably small example tomorrow; right now
I've just discovered this problem and can only show the problem in
the diffs of disassembler listings between the two builds of a Linux
kernel with binutils 2.8.1 and cvs-binutils.

  Ralf

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: HI16 / LO16 relocations.
  1999-08-03 15:10 HI16 / LO16 relocations Ralf Baechle
@ 1999-08-03 15:40 ` Mark Mitchell
  1999-08-03 16:01   ` Ralf Baechle
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Mitchell @ 1999-08-03 15:40 UTC (permalink / raw)
  To: ralf; +Cc: binutils, linux, linux-mips, linux-mips

>>>>> "Ralf" == Ralf Baechle <ralf@uni-koblenz.de> writes:

    Ralf> Mark, for now I'm just posting this in the hope it may ring
    Ralf> a bell.  It seems like HI16 / LO16 relocation pairs are not
    Ralf> handled correctly This may result in ``la $reg, symbol''
    Ralf> ending up after the final link as ``la $reg, symbol +
    Ralf> 0x10000''.

We're running into a lot more problems than I'd hoped for.  I'm
becoming embarassed.  The best redeeming action is fix the problems
with all possible alacrity; I'll try my best.  I do really think we're
getting close.  I appreciate your testing.

As soon as you get a test-case, I'll take a look at this.  It's fine
even it's big, as long as you can point at the exact place that goes
wrong; I'd really like to get this work behind me, and get everything
back to a more stable state.  've compiled *millions* of lines of code
on IRIX6 with the new linker without a problem; obviously the
relocation patterns are very different from the N32/N64 ABI to the
older ABIs.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: HI16 / LO16 relocations.
  1999-08-03 15:40 ` Mark Mitchell
@ 1999-08-03 16:01   ` Ralf Baechle
  0 siblings, 0 replies; 3+ messages in thread
From: Ralf Baechle @ 1999-08-03 16:01 UTC (permalink / raw)
  To: Mark Mitchell; +Cc: binutils, linux, linux-mips, linux-mips

On Tue, Aug 03, 1999 at 03:42:36PM -0700, Mark Mitchell wrote:

> As soon as you get a test-case, I'll take a look at this.  It's fine
> even it's big, as long as you can point at the exact place that goes
> wrong; I'd really like to get this work behind me, and get everything
> back to a more stable state.  've compiled *millions* of lines of code
> on IRIX6 with the new linker without a problem; obviously the
> relocation patterns are very different from the N32/N64 ABI to the
> older ABIs.

I think the core differences are probably that I tried to compile non-pic
code and code which tries to use GNU extensions.  I intend to recompile
the entire Linux distribution with this new linker which probably will
trigger a few more bugs according to my past experience.  Finally the
Linux/MIPS64 kernel will exercise non-PIC 64-bit code - hopefully
without triggering any new bugs ...

  Ralf

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1999-08-03 16:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-08-03 15:10 HI16 / LO16 relocations Ralf Baechle
1999-08-03 15:40 ` Mark Mitchell
1999-08-03 16:01   ` Ralf Baechle

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).