From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] BUG!!! in Plan9 compiler!
Date: Sat, 24 Apr 2010 20:31:11 -0400 [thread overview]
Message-ID: <174c125c7e2b6e1de7c2a782868a819f@kw.quanstro.net> (raw)
In-Reply-To: <20100424185913.9A9CC5B42@mail.bitblocks.com>
> Is this behaviour really useful for anything? Is there
> anything in plan9 code that relies on this behaviour in a
> critical way? I suspect this rule can be changed without
> impacting plan 9 code much (which as a rule is of much higher
> quality than most open source code) and we already know
> programs ported to p9p work fine.
the network stack has a few bits that don't work without
changes, as i painfully learned with 9vx.
if a patch to the c compiler showed up that did this and
were distributed with sources, i would only consider using
it only if there were an automatic way of locating code that
might change behavior with a lowish false positive rate and
a verifiably zero false negative rate. even then it would be
very painful as i would need to verify that the system and
all our shipping code works properly with new rules. i see
little upside.
in short, That Boat Has Sailed.
- erik
prev parent reply other threads:[~2010-04-25 0:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 15:29 tlaronde
2010-04-22 17:03 ` Bakul Shah
2010-04-22 17:36 ` tlaronde
2010-04-22 17:50 ` tlaronde
2010-04-22 19:08 ` geoff
2010-04-22 19:32 ` tlaronde
2010-04-22 20:07 ` Bakul Shah
2010-04-22 21:15 ` tlaronde
2010-04-22 21:26 ` tlaronde
2010-04-22 22:49 ` Bakul Shah
2010-04-23 7:42 ` tlaronde
2010-04-23 18:53 ` C H Forsyth
2010-04-23 18:51 ` tlaronde
2010-04-23 20:08 ` Bakul Shah
2010-04-23 20:46 ` ron minnich
2010-04-23 21:44 ` erik quanstrom
2010-04-23 22:34 ` erik quanstrom
2010-04-24 18:59 ` Bakul Shah
2010-04-24 21:47 ` Charles Forsyth
2010-04-25 0:31 ` erik quanstrom [this message]
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=174c125c7e2b6e1de7c2a782868a819f@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).