All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] sparc64 (common & specific files)
Date: Thu, 14 Jul 2005 10:27:00 +0200	[thread overview]
Message-ID: <200507141027.00171.okuji@enbug.org> (raw)
In-Reply-To: <23f63ec505913b950c9734eee2477a7b@penguinppc.org>

On Thursday 14 July 2005 02:43, Hollis Blanchard wrote:
> On Jul 13, 2005, at 5:15 PM, Vincent Pelletier wrote:
> > Marco Gerards wrote:
> >> For which reason?
> >>
> >> But if it should be more precise, it should be a grub_uint64_t.
> >
> > If the architecture give us a 32 bit number, we won't invent the
> > remaining 32 bits...
>
> We don't invent them; they are 0.

Please do not extend it to 64-bit on i386. 64-bit variables consume more 
registers and enlarge the binary code. GRUB does not have to be very precise 
about the time, so I prefer 32-bit here for all architectures. If you have a 
good reason to use 64-bit except that the native representation is 64-bit, 
let me know.

Okuji



  reply	other threads:[~2005-07-14  9:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 18:57 [PATCH] sparc64 (common & specific files) Vincent Pelletier
2005-07-13  7:34 ` Vincent Pelletier
2005-07-13  8:55 ` Vincent Pelletier
2005-07-13 16:21   ` Marco Gerards
2005-07-13 21:02     ` Vincent Pelletier
2005-07-13 21:49       ` Marco Gerards
2005-07-13 22:15         ` Vincent Pelletier
2005-07-14  0:43           ` Hollis Blanchard
2005-07-14  8:27             ` Yoshinori K. Okuji [this message]
2005-07-13 16:19 ` Marco Gerards
2005-07-13 20:59   ` Vincent Pelletier
2005-07-27  3:58     ` missing prefix not fatal Hollis Blanchard
2005-07-27  7:27       ` Vincent Pelletier

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=200507141027.00171.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /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.