From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Don't Plan 9 C compiler initialize the rest of member of a?struct?
Date: Tue, 2 Apr 2019 17:37:01 +0100 [thread overview]
Message-ID: <CAOw7k5gH98yGhE+BtCCB8eDBbzRhgSD=R6bevJt1V3uRNrmkmA@mail.gmail.com> (raw)
In-Reply-To: <20190402162558.GA14506@alice>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
covered and covered1
On Tue, 2 Apr 2019 at 17:26, Anthony Martin <ality@pbrane.org> wrote:
> Charles Forsyth <charles.forsyth@gmail.com> once said:
> > I didn't look at the code closely enough earlier, but remembered
> something
> > from years ago this morning. It's a bug. It isn't platform specific.
> > There is an existing fix in 9front (I think it came from there) but it's
> > horrible. Still, better a horrible fix than buggy code, so I'll apply it
> to
> > the 9legacy version as well.
>
> It's in /sys/src/cmd/cc/dcl.c:/^contig
>
> What was horrible about the fix?
>
> Anthony
>
>
[-- Attachment #2: Type: text/html, Size: 1017 bytes --]
next prev parent reply other threads:[~2019-04-02 16:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 15:32 [9fans] Don't Plan 9 C compiler initialize the rest of member of a struct? Kyohei Kadota
2019-04-01 23:49 ` Skip Tavakkolian
2019-04-02 14:44 ` Kyohei Kadota
2019-04-02 0:26 ` Jeremy O'Brien
2019-04-02 0:35 ` Charles Forsyth
2019-04-02 0:35 ` [9fans] Don't Plan 9 C compiler initialize the rest of member of a?struct? Kurt H Maier
2019-04-02 1:20 ` Dan Cross
2019-04-02 2:22 ` Kurt H Maier
2019-04-02 3:06 ` Skip Tavakkolian
2019-04-02 8:02 ` David du Colombier
2019-04-02 10:38 ` Charles Forsyth
2019-04-02 16:25 ` Anthony Martin
2019-04-02 16:37 ` Charles Forsyth [this message]
2019-04-02 14:52 ` [9fans] Don't Plan 9 C compiler initialize the rest of member of a struct? Kyohei Kadota
2019-04-02 15:02 ` Skip Tavakkolian
2019-04-02 15:14 ` Skip Tavakkolian
2019-04-02 16:18 ` Devon H. O'Dell
2019-04-02 19:57 ` Charles Forsyth
2019-04-02 15:04 ` Charles Forsyth
2019-04-02 15:16 ` Kyohei Kadota
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='CAOw7k5gH98yGhE+BtCCB8eDBbzRhgSD=R6bevJt1V3uRNrmkmA@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--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).