From: Ray Lee <ray-lk@madrabbit.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: viro@parcelfarce.linux.theplanet.co.uk, tomstdenis@yahoo.com,
eger@havoc.gtf.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 0xdeadbeef vs 0xdeadbeefL
Date: Tue, 06 Jul 2004 23:12:57 -0700 [thread overview]
Message-ID: <1089180777.4373.186.camel@orca.madrabbit.org> (raw)
In-Reply-To: <orisd0qrxi.fsf@livre.redhat.lsd.ic.unicamp.br>
On Tue, 2004-07-06 at 22:58, Alexandre Oliva wrote:
> Are you sure? I've seen K&R C compilers for 32-bit platforms in which
> 0xdeadbeef had type *signed* int, as opposed to unsigned int.
K&R pre-ANSI (i.e., K&R first edition) allowed this. K&R second edition,
a.k.a. ANSI C clarifies this substantially, as per my previous two
messages on the topic.
> I thought the preference for an unsigned type in this case was
> introduced in ISO C90, but it might as well have been a bug in that
> compiler. Although I'm told other compilers display similar behavior.
File a bug.
Ray
next prev parent reply other threads:[~2004-07-07 6:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 2:05 0xdeadbeef vs 0xdeadbeefL Ray Lee
2004-07-07 3:02 ` viro
2004-07-07 5:58 ` Alexandre Oliva
2004-07-07 6:12 ` Ray Lee [this message]
2004-07-07 5:55 ` Alexandre Oliva
2004-07-07 6:08 ` Ray Lee
2004-07-07 6:48 ` viro
2004-07-07 17:58 ` Alexandre Oliva
2004-07-12 17:31 ` H. Peter Anvin
2004-07-07 7:30 ` Tomas Szepe
2004-07-07 14:34 ` Jan-Benedict Glaw
2004-07-12 17:50 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 21:56 David Eger
2004-07-07 0:06 ` tom st denis
2004-07-07 3:00 ` viro
2004-07-07 11:10 ` tom st denis
2004-07-07 14:22 ` viro
2004-07-07 18:47 ` tom st denis
2004-07-07 16:30 ` Gabriel Paubert
2004-07-07 18:41 ` tom st denis
2004-07-07 18:47 ` Christoph Hellwig
2004-07-07 18:53 ` tom st denis
2004-07-07 23:17 ` Harald Arnesen
2004-07-08 6:15 ` David Weinehall
2004-07-08 17:16 ` Horst von Brand
2004-07-10 1:52 ` Andrew Rodland
2004-07-07 0:38 ` Richard B. Johnson
2004-07-07 4:52 ` David Eger
2004-07-07 11:40 ` Richard B. Johnson
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=1089180777.4373.186.camel@orca.madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=aoliva@redhat.com \
--cc=eger@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomstdenis@yahoo.com \
--cc=viro@parcelfarce.linux.theplanet.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox