linux-mips
[Top] [All Lists]

Re: Kernel crash on boot with current cvs (todays)

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: Kernel crash on boot with current cvs (todays)
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Sat, 16 Jun 2001 11:24:18 +0200
Cc: Keith Owens <kaos@melbourne.sgi.com>, Florian Lohoff <flo@rfc822.org>, Raoul Borenius <borenius@shuttle.de>, linux-mips@oss.sgi.com
In-reply-to: <Pine.GSO.3.96.1010613153740.9854H-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jun 13, 2001 at 03:44:28PM +0200
References: <20010613140550.B31221@bacchus.dhis.org> <Pine.GSO.3.96.1010613153740.9854H-100000@delta.ds2.pg.gda.pl>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Wed, Jun 13, 2001 at 03:44:28PM +0200, Maciej W. Rozycki wrote:

>  The point is whether addresses should be extended at all if a 32-bit
> target is selected.  IMHO -- not, that's a limitation of BFD when
> configured for both a 32-bit and a 64-bit target and it should be fixed
> sooner or later (at least it's on my to-do list for some time).  BFD is
> free to handle addresses as it likes internally, be it 64-bit or 32-bit,
> but they should be truncated on final output to a 32-bit target, as they
> already are for certain cases. 

Agreed, that'd be much more readable for humans.  For processing by
software having some canonical form, that is 64-bit would be a bit more
handy though.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>