Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Keith Owens <kaos@melbourne.sgi.com>,
	Florian Lohoff <flo@rfc822.org>,
	Raoul Borenius <borenius@shuttle.de>,
	linux-mips@oss.sgi.com
Subject: Re: Kernel crash on boot with current cvs (todays)
Date: Sat, 16 Jun 2001 11:24:18 +0200	[thread overview]
Message-ID: <20010616112418.B21117@bacchus.dhis.org> (raw)
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

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

  parent reply	other threads:[~2001-06-16 11:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11  3:53 ` Keith Owens
2001-06-11 19:12   ` Florian Lohoff
2001-06-12  1:01     ` Maciej W. Rozycki
2001-06-12  1:01       ` Keith M Wesolowski
2001-06-12  1:22         ` Maciej W. Rozycki
2001-06-12  2:05       ` Keith Owens
2001-06-11  4:42 ` Ralf Baechle
2001-06-11 14:50   ` Raoul Borenius
2001-06-12 10:09     ` Florian Lohoff
2001-06-12 11:53       ` Ralf Baechle
2001-06-12 16:37         ` H . J . Lu
     [not found]         ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56           ` Florian Lohoff
2001-06-13 11:34             ` Keith Owens
2001-06-13 12:05               ` Ralf Baechle
2001-06-13 12:19                 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16  9:22                   ` Ralf Baechle
2001-06-27  2:21                   ` ksymoops changes for mips Keith Owens
2001-06-28 14:32                     ` Thiemo Seufer
2001-07-31  3:57                       ` Keith Owens
2001-07-31  4:30                         ` Keith Owens
2001-08-03  6:10                       ` Keith Owens
2001-08-03 10:07                         ` Thiemo Seufer
2001-06-13 13:44                 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07                   ` Keith Owens
2001-06-13 15:08                     ` Maciej W. Rozycki
2001-06-16  9:24                   ` Ralf Baechle [this message]
2001-06-13 11:37             ` Raoul Borenius
2001-06-13 11:46               ` Keith Owens
2001-06-13 11:46                 ` Keith Owens
2001-06-13 13:16                 ` Raoul Borenius

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=20010616112418.B21117@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=borenius@shuttle.de \
    --cc=flo@rfc822.org \
    --cc=kaos@melbourne.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    /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