All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 1/7]: Fix sparc64 setjmp implementation.
Date: Sat, 07 Mar 2009 00:56:43 -0500	[thread overview]
Message-ID: <20090307005643.u3urxp4beo4k8o84-cebfxv@webmail.spamcop.net> (raw)
In-Reply-To: <20090306.163953.27529500.davem@davemloft.net>

Quoting David Miller <davem@davemloft.net>:

>> I was considering making grub_size_t long and grub_ssize_t unsigned
>> long.  I remember that it required many changes in string formats, so I
>> didn't feel it would be justified.  But we could try it again.
>
> You should use whatever is the appropriate size_t/ssize_t type on
> the given platform+ABI, and that way GRUB could use "%Zd" and/or
> "%zd" throughout.  Was that the plan?

No, the plan was to use long.  We don't support architectures where  
long and size_t have different sizes.  I'm not aware of such  
architectures.  I don't care about win64, as it would need some very  
special handling (perhaps redefinition of long).

I was trying to fix an inconsistency of the userspace, where size_t  
can be unsigned int or unsigned long.  Perhaps the plan was too  
ambitious.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2009-03-07  5:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  2:15 [PATCH 1/7]: Fix sparc64 setjmp implementation David Miller
2009-03-04 10:59 ` Vesa Jääskeläinen
2009-03-04 11:05   ` David Miller
2009-03-04 11:34 ` Vesa Jääskeläinen
2009-03-04 11:36   ` David Miller
2009-03-04 15:58     ` Javier Martín
2009-03-04 21:02       ` David Miller
2009-03-05 13:04         ` Isaac Dupree
2009-03-05 13:24           ` David Miller
2009-03-06 18:55           ` Robert Millan
2009-03-06 19:03             ` Pavel Roskin
2009-03-07  0:39               ` David Miller
2009-03-07  5:56                 ` Pavel Roskin [this message]
2009-03-07 10:38                   ` Robert Millan
2009-03-07 14:29                     ` David Miller
2009-03-07  0:34             ` David Miller
2009-03-07 10:39               ` Robert Millan

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=20090307005643.u3urxp4beo4k8o84-cebfxv@webmail.spamcop.net \
    --to=proski@gnu.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.