From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] another compiler bug (another try to send this coherently)
Date: Mon, 16 Jul 2001 15:41:30 +0200 [thread overview]
Message-ID: <00ea01c10dfd$04f226b0$3cf7c6d4@SOMA> (raw)
In-Reply-To: <00a701c10df6$03a73450$3cf7c6d4@SOMA>
do you define implementation as the compiler or the
whole system? the other guy seems to be doing stupid
stuff with APE or some ANSI (ie. non native plan 9
compiler [ken C]):
#include <stdio.h>
#include <stdlib.h>
int
main()
{
static unsigned char tab[1] = { 0x80 };
static int x = 0x80;
printf("%d %d\n", tab[0] << 24 >> 31, x << 24 >> 31);
exit(EXIT_SUCCESS);
}
why he just can't read the doc and stop fucking with stupid
shifts is beyond me? is this C programming 101?
i would class the compiler as the implementation, 'cos
you could have multiple compilers (and you do) on plan 9
or on some random unix you could have the native compiler
and then install gcc (god forbid).
i tend to err on the side of caution (ie. paranoia/overkill)
so i don't bitten by such glop.
next prev parent reply other threads:[~2001-07-16 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 11:13 rog
2001-07-16 12:51 ` Boyd Roberts
2001-07-16 13:41 ` Boyd Roberts [this message]
2001-07-16 13:44 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 15:51 forsyth
2001-07-18 8:43 ` Douglas A. Gwyn
2001-07-14 3:26 Mike Haertel
2001-07-16 9:05 ` Douglas A. Gwyn
2001-07-16 9:38 ` Boyd Roberts
2001-07-16 18:34 ` Mike Haertel
2001-07-16 18:52 ` Boyd Roberts
2001-07-16 19:21 ` Mike Haertel
2001-07-16 19:47 ` Boyd Roberts
2001-07-17 15:16 ` Douglas A. Gwyn
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='00ea01c10dfd$04f226b0$3cf7c6d4@SOMA' \
--to=boyd@fr.inter.net \
--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).