public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: cpu-2.5.64-1
Date: Sun, 16 Mar 2003 11:14:09 -0800	[thread overview]
Message-ID: <20030316191409.GK20188@holomorphy.com> (raw)
In-Reply-To: <200303161242.h2GCg1PO001746@eeyore.valparaiso.cl>

William Lee Irwin III <wli@holomorphy.com> said:
>> Another thought I had was wrapping things in structures for both small
>> and large, even UP systems so proper typechecking is enforced at all
>> times. That would probably need a great deal of arch sweeping to do,
>> especially as a number of arches are UP-only (non-SMP case's motive #2).

On Sun, Mar 16, 2003 at 08:42:01AM -0400, Horst von Brand wrote:
> AFAIU, gcc doesn't put structures in registers (even when they fit).

Bugreport and/or wishlist time.


-- wli

      reply	other threads:[~2003-03-16 19:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  4:24 cpu-2.5.64-1 William Lee Irwin III
2003-03-11  7:17 ` cpu-2.5.64-1 Zwane Mwaikambo
2003-03-11  8:25   ` cpu-2.5.64-1 Zwane Mwaikambo
2003-03-16  7:39 ` cpu-2.5.64-1 Keith Owens
2003-03-16  8:36   ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16  9:19     ` cpu-2.5.64-1 Keith Owens
2003-03-16  9:46       ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 10:10       ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 11:12         ` cpu-2.5.64-1 Keith Owens
2003-03-16 11:32           ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 11:53             ` cpu-2.5.64-1 Keith Owens
2003-03-16 12:00               ` cpu-2.5.64-1 William Lee Irwin III
2003-03-16 12:42             ` cpu-2.5.64-1 Horst von Brand
2003-03-16 19:14               ` William Lee Irwin III [this message]

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=20030316191409.GK20188@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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