From: Robert Noland <rnoland@2hip.net>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sourceforge.net,
"Matthew W. S. Bell" <matthew@bells23.org.uk>
Subject: Re: [PATCH] typdef uintptr_t drm_handle_t; unsigned int is wrong on 64-bit.
Date: Tue, 06 Apr 2010 15:14:39 -0500 [thread overview]
Message-ID: <4BBB962F.2070909@2hip.net> (raw)
In-Reply-To: <q2g21d7e9971004050046td05602fci4ab1dde6e1d92ef9@mail.gmail.com>
Dave Airlie wrote:
> On Sat, Apr 3, 2010 at 11:09 PM, Matthew W. S. Bell
> <matthew@bells23.org.uk> wrote:
>> On Sat, 2010-04-03 at 08:49 +0100, Dave Airlie wrote:
>>> No, its "designed" as is. We can't change it now as its ABI. We make sure
>>> we only use 32-bit handles anyways.
>
> The thing is "unsigned int" is correct for the handles, they are defined to
> be 32-bit numbers no matter what system they are on, its the use of the
> void * that is actually the problem.
>
> Its probably not documented well anywhere, though I think the handles are
> 32-bit is written down somewhere.
No, they are not. They are only 32bit on linux. The size of handle
varies with architecture on FreeBSD as it is passed to mmap as an offset
into memory. Honestly, I would prefer that they always be 64bits, but
that would break ABI... The dual meaning of handle has frustrated me
more than a few times.
robert.
> Dave.
>> OK, is this documented anywhere, as I'd like to pull some of that into a
>> comment? (It appears, on a casual glance, that this type is not used in
>> the kernel ABI, but only in the libdrm, and associates?, ABI, so could
>> be changed if the SONAME got bumped and anyone cared.)
>>
>> Matthew
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> --
>> _______________________________________________
>> Dri-devel mailing list
>> Dri-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dri-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-04-06 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 1:59 [PATCH] typdef uintptr_t drm_handle_t; unsigned int is wrong on 64-bit Matthew W. S. Bell
2010-04-03 7:49 ` Dave Airlie
2010-04-03 13:09 ` Matthew W. S. Bell
2010-04-05 7:46 ` Dave Airlie
2010-04-06 20:14 ` Robert Noland [this message]
2010-04-09 2:05 ` [PATCH] drm_handle_t type Matthew W. S. Bell
2010-04-10 18:30 ` Matthew W. S. Bell
2010-04-11 14:10 ` Robert Noland
2010-04-13 23:19 ` Matthew W. S. Bell
2010-04-14 3:26 ` Robert Noland
2010-04-14 3:32 ` Robert Noland
2010-04-14 3:46 ` Dave Airlie
2010-04-14 17:36 ` Robert Noland
2010-04-14 16:15 ` Matthew W. S. Bell
2010-04-03 21:57 ` [PATCH] typdef uintptr_t drm_handle_t; unsigned int is wrong on 64-bit Matthew W. S. Bell
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=4BBB962F.2070909@2hip.net \
--to=rnoland@2hip.net \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=matthew@bells23.org.uk \
/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.