Date: Mon, 8 Jun 2009 12:55:47 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 Message-ID: <uMBnEiAEdz5aAnVQx9%2B%2BqCSd2Gs@j4OYE6OL8eALCd4BvSxIfwgoxSc> In-Reply-To: <20090608084107.GE9529@server.vk2pj.dyndns.org> References: <20090608025715.499087302F@freebsd-current.sentex.ca> <8LPG99US2/4EsGlonyfMSkDb40o@XX1fo6zQUfC4h0jjRC6IBz3oNH4> <20090608084107.GE9529@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mon, Jun 08, 2009 at 06:41:07PM +1000, Peter Jeremy wrote:
> On 2009-Jun-08 11:00:56 +0400, Eygene Ryabinkin <rea-fbsd@codelabs.ru> wrote:
> > ifr->ifr_data = (caddr_t)(size_t)options;
> >-----
> >will be more correct and will disable this warning -- it will convert
> >u_int to the proper type that will be able to carry addresses for the
> >given platform.
>
> Whilst I notice this specific problem has been resolved differently,
> for future reference, you should use [u]intptr_t rather than [s]size_t
> for this purpose.
Thanks -- I had trouble with recalling the name of 'intptr_t', so used
'size_t'. Just curious -- are there platforms/compilers on that these
two are really different in sizes? Or this is pure semantical difference?
--
Eygene
_ ___ _.--. #
\`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual
)/' _/ \ `-_, / # while single-stepping the kernel.
`-'" `"\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / # -- FreeBSD Developers handbook
{_.-``-' {_/ #
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uMBnEiAEdz5aAnVQx9%2B%2BqCSd2Gs>