From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Mixfs: potential bug?
Date: Wed, 12 Feb 2020 16:33:39 -0800 [thread overview]
Message-ID: <CAHwi9byyMsBUSzhj+zsG-JiHsda_e2kFKoU0D=24a23nkco7cg@mail.gmail.com> (raw)
In-Reply-To: <CAHjwAuxsW9J2faquv2djaedf9fT9OgFXc6FRfBH29vQBaRm6fA@mail.gmail.com>
I've had trouble with mixfs but haven't looked into it closely yet.
sometimes it just screws up and starts missing data or something.
On Wed, Feb 12, 2020 at 4:21 PM Silas McCroskey <inkswinc@gmail.com> wrote:
>
> http://doc.cat-v.org/plan_9/4th_edition/papers/comp
>
> The "Extensions" section goes over this compiler extension:
>
> structs-within-structs declared without a name allow their members to
> be accessed directly, so
> qlock(s)
> does the same thing as
> qlock(s->Lock)
> since the "locked" member used by qlock is accessible to both.
>
> This is a compiler extension rather than pointer tricks, so it does
> not depend on ordering within the struct (as displayed in the
> Extensions section itself, where Lock is the last member of the outer
> struct).
>
> - sam-d
>
> On Wed, Feb 12, 2020 at 4:07 PM Trevor Higgins
> <plan9fullfrontal@qs.co.nz> wrote:
> >
> > Looking at the code for audio/mixfs (mixfs.c)
> >
> > The code uses qlock(s) where s is: struct Stream*.
> >
> > In the structure ,shouldn't the QLock member of the structure be the
> > first member in the structure?
> > If not so, then why does it not matter?
> >
> > Thanks.
> >
> > --
> >
--
http://echoline.org
next prev parent reply other threads:[~2020-02-13 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 20:51 Libpng and Zlib updates on the ports tree Lucas Francesco
2020-02-12 21:01 ` [9front] " ori
2020-02-13 0:06 ` Mixfs: potential bug? Trevor Higgins
2020-02-13 0:21 ` [9front] " Silas McCroskey
2020-02-13 0:33 ` Eli Cohen [this message]
2020-02-13 1:22 ` Trevor Higgins
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='CAHwi9byyMsBUSzhj+zsG-JiHsda_e2kFKoU0D=24a23nkco7cg@mail.gmail.com' \
--to=echoline@gmail.com \
--cc=9front@9front.org \
/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).