From: Albert Cahalan <albert@users.sf.net>
To: davidm@hpl.hp.com
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
Andrew Morton OSDL <akpm@osdl.org>
Subject: Re: [patch] u64 casts
Date: 27 Feb 2004 17:53:44 -0500 [thread overview]
Message-ID: <1077922424.2232.54.camel@cube> (raw)
In-Reply-To: <16447.58524.257563.252138@napali.hpl.hp.com>
On Fri, 2004-02-27 at 19:45, David Mosberger wrote:
> >>>>> On 27 Feb 2004 17:16:53 -0500, Albert Cahalan <albert@users.sourceforge.net> said:
>
> Albert> Supposing that this is the case, you may get warnings.
>
> Well, then do it on your own kernel/system. I'm not interested in
> spending time on this now, so please don't touch ia64 unless you
> verified that all the other pieces are in place.
Remember, that is only if all of:
1. glibc improperly uses raw kernel headers
2. usage is in such a way that warnings happen
3. you rebuild glibc with these kernel headers
If this is really the case, the warnings may be
eliminated by running a 1-line sed script over
the headers as they are imported into glibc.
It's something like this: s/__u64/u_int64_t/
In return, you can have type-safety w/o warnings
during the kernel build.
In my example, suppose that foo is a pointer
to u64. You'd like to print the u64. If by
mistake you use the pointer itself, you won't
be getting a warning. The cast hides it.
next prev parent reply other threads:[~2004-02-28 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 20:58 [patch] u64 casts Albert Cahalan
2004-02-28 0:18 ` David Mosberger
2004-02-27 22:16 ` Albert Cahalan
2004-02-28 0:45 ` David Mosberger
2004-02-27 22:53 ` Albert Cahalan [this message]
2004-02-28 7:44 ` David S. Miller
2004-02-28 10:42 ` Jakub Jelinek
2004-02-28 14:46 ` [patch] new version, u64 cast avoidance Albert Cahalan
2004-02-28 23:58 ` Benjamin Herrenschmidt
2004-02-28 23:59 ` Benjamin Herrenschmidt
2004-02-28 22:21 ` Albert Cahalan
2004-02-29 1:08 ` Benjamin Herrenschmidt
2004-02-28 23:49 ` Albert Cahalan
2004-02-29 3:25 ` Matt Mackall
2004-02-29 1:01 ` [patch] 3rd " Albert Cahalan
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=1077922424.2232.54.camel@cube \
--to=albert@users.sf.net \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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