From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] compiler bug
Date: Thu, 12 Jul 2001 14:19:03 +0100 [thread overview]
Message-ID: <20010712131622.835AA199EC@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 177 bytes --]
i take it back. it goes wrong earlier than that, in lex.c
where it does mark it as ulong, but only after encouraging
convvtox to force it negative in the underlying vlong.
[-- Attachment #2: Type: message/rfc822, Size: 3968 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 153 bytes --]
the compiler correctly marks it as unsigned int and uses the
correct shift operator and types in the resulting tree, but it goes wrong
a bit later.
[-- Attachment #2.1.2: Type: message/rfc822, Size: 2241 bytes --]
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] compiler bug
Date: Thu, 12 Jul 2001 12:21:51 +0200
Message-ID: <063601c10abc$775b3500$c0b7c6d4@SOMA>
> In this case, 0x80000000 is not a representable value of type int,
> but is representable as unsigned int, so it should have that type.
eh? it most certainly _can_ be represented as an int
if your machine has 32 bit ints. all the world's a vax :)
until you hit the stupidity digital did with compiler
for the alpha. int was always >= 16 bits and intended to
be the native machine 'word' size.
next reply other threads:[~2001-07-12 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 13:19 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-30 13:03 [9fans] Compiler bug Julius Schmidt
2014-05-30 14:56 ` Charles Forsyth
2001-07-14 5:39 [9fans] compiler bug David Gordon Hogan
2001-07-14 7:52 ` Mike Haertel
2001-07-12 10:33 forsyth
2001-07-12 6:27 Mike Haertel
2001-07-12 10:21 ` Boyd Roberts
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=20010712131622.835AA199EC@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).