LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Howells <dhowells@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Arch Mailing List <linux-arch@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [PATCH 1/2] Add C99-style constructor macros for specific-sized integers
Date: Mon, 03 Mar 2008 09:03:35 -0800 [thread overview]
Message-ID: <47CC2F67.80003@zytor.com> (raw)
In-Reply-To: <20080303124050.GA24841@uranus.ravnborg.org>
Sam Ravnborg wrote:
>
> And in linux/const.h we have yet another variant:
> /* Some constant macros are used in both assembler and
> * C code. Therefore we cannot annotate them always with
> * 'UL' and other type specifiers unilaterally. We
> * use the following macros to deal with this.
> *
> * Similarly, _AT() will cast an expression with a type in C, but
> * leave it unchanged in asm.
> */
>
> #ifdef __ASSEMBLY__
> #define _AC(X,Y) X
> #define _AT(T,X) X
> #else
> #define __AC(X,Y) (X##Y)
> #define _AC(X,Y) __AC(X,Y)
> #define _AT(T,X) ((T)(X))
> #endif
>
> Not as typestrict as hpa's and arm's version but
> used in a few placed already.
>
These, unfortunately, don't solve the issue of gcc warnings, and you
don't want to make them paste ULL on before the cast, since I think
they're used with non-simple constants.
-hpa
next prev parent reply other threads:[~2008-03-03 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 0:09 H. Peter Anvin
2008-03-03 0:09 ` [PATCH 2/2] Use U64_C() instead of casts in kernel/time.c H. Peter Anvin
2008-03-03 2:38 ` [PATCH 1/2] Add C99-style constructor macros for specific-sized integers Matthew Wilcox
2008-03-03 4:43 ` H. Peter Anvin
2008-03-03 6:20 ` Al Viro
2008-03-03 6:12 ` H. Peter Anvin
2008-03-03 6:32 ` Al Viro
2008-03-03 6:28 ` H. Peter Anvin
2008-03-03 3:20 ` Segher Boessenkool
2008-03-03 4:14 ` David Brownell
2008-03-03 4:50 ` H. Peter Anvin
2008-03-03 4:45 ` H. Peter Anvin
2008-03-03 20:23 ` Segher Boessenkool
2008-03-03 10:57 ` David Howells
2008-03-03 11:43 ` Russell King
2008-03-03 12:40 ` Sam Ravnborg
2008-03-03 17:03 ` H. Peter Anvin [this message]
2008-03-03 12:15 ` David Howells
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=47CC2F67.80003@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--subject='Re: [PATCH 1/2] Add C99-style constructor macros for specific-sized integers' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).