From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Stan C. Smith" <stan.smith-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: 'Sasha Khapyorsky'
<sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org,
'linux-rdma' <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm - use uintptr_t instead of unsigned long
Date: Thu, 8 Oct 2009 11:55:08 -0600 [thread overview]
Message-ID: <20091008175508.GY5191@obsidianresearch.com> (raw)
In-Reply-To: <B4D2EF981C584307AA9204669ECE3F31-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
On Thu, Oct 08, 2009 at 10:12:03AM -0700, Stan C. Smith wrote:
> If you can live with uintptr_t for
> __WORDSIZE == 32 being 'unsigned int' (see stdint.h)
> __WORDSIZE == 64 uintptr_t is 'unsigned long int'
> then we could skip the ifdef __GNUC__ and just replace 'unsigned long' with uintptr_t.
uinptr_t is the appropriate ISO C99 type for this, every platform
should use it.
Non-standard names like st_ptr_t should just be eradicated.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-08 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 17:12 [PATCH] opensm - use uintptr_t instead of unsigned long Stan C. Smith
[not found] ` <B4D2EF981C584307AA9204669ECE3F31-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-10-08 17:55 ` Jason Gunthorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 16:23 Stan C. Smith
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=20091008175508.GY5191@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ofw-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=stan.smith-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox