From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cc nit?
Date: Sat, 30 Jun 2012 15:15:05 -0700 [thread overview]
Message-ID: <20120630221505.8D6E2B82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 30 Jun 2012 17:37:37 EDT." <c9c70b472e2a3d68dd25f5f850e0b8ef@brasstown.quanstro.net>
On Sat, 30 Jun 2012 17:37:37 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> On Sat Jun 30 17:34:47 EDT 2012, bakul@bitblocks.com wrote:
> > On Sat, 30 Jun 2012 17:25:21 EDT erik quanstrom <quanstro@quanstro.net> wr
> ote:
> > > i haven't tracked down thie issue yet, but it appears that ?c
> > > generate unparsable acid output
> > >
> > > ; cat > void.c
> > > typedef struct PNOTIFY PNOTIFY
> > >
> > > struct PNOTIFY {
> > > void emptiness;
> > > }; ^^^^
> >
> > Why would you do that?
>
> because there's nothing that needs to be saved there for the k10
> architecture.
I think this void exension is just plain broken. Try
#include <u.h>
#include <libc.h>
void foo; void bar;
main() { print("%p, %p\n", &foo, &bar);
It fails in the link stage for me.
I would've tried
struct PNOTIFY {
char nothingness[0];
};
as it more directly expresses the intent (at least to me) but
that doesn't work either.
next prev parent reply other threads:[~2012-06-30 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 21:25 erik quanstrom
2012-06-30 21:33 ` Bakul Shah
2012-06-30 21:37 ` erik quanstrom
2012-06-30 22:15 ` Bakul Shah [this message]
2012-07-01 13:47 ` erik quanstrom
2012-07-01 16:54 ` Comeau At9Fans
2012-07-01 20:39 ` Charles Forsyth
2012-07-01 22:22 ` Comeau At9Fans
2012-07-01 22:32 ` Charles Forsyth
2012-07-01 22:34 ` Charles Forsyth
2012-07-02 0:21 ` Comeau At9Fans
2012-07-02 0:18 ` Comeau At9Fans
2012-07-02 7:42 ` Charles Forsyth
2012-07-02 7:45 ` Charles Forsyth
[not found] ` <CAE9W7-iFxd6ysP4cxRcGVuLT0n+SY2r4XjOTVpjpXi292v4WWQ@mail.gmail.c>
2012-07-01 22:45 ` erik quanstrom
2012-07-02 0:24 ` Comeau At9Fans
[not found] ` <CAE9W7-gZsWHuspmwBw0qU_djkiDhAF6hA2zLU3Ms=xiO1j5LXQ@mail.gmail.c>
2012-07-01 16:57 ` erik quanstrom
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=20120630221505.8D6E2B82A@mail.bitblocks.com \
--to=bakul@bitblocks.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).