From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 8c funny
Date: Thu, 26 May 2005 13:16:51 -0400 [thread overview]
Message-ID: <ee9e417a0505261016798fd0bd@mail.gmail.com> (raw)
In-Reply-To: <2b6ab41511e81ba9e112d138defae02b@coraid.com>
the real problem is that the compiler doesn't
do used and not set on vlongs, because they
were originally treated a lot more like structures
than scalars.
russ
On 5/26/05, Brantley Coile <brantley@coraid.com> wrote:
> term% 8c -FVw busted.c
> warning: busted.c:5 used and not set: b
> term% cat busted.c
> #include <u.h>
> #include <libc.h>
>
> void
> main(void)
> {
> vlong a;
>
> int b;
>
> if (a == 0)
> exits(nil);
> if (b == 0)
> exits(nil);
> exits(nil);
> }
>
next prev parent reply other threads:[~2005-05-26 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 17:10 Brantley Coile
2005-05-26 17:16 ` Russ Cox [this message]
2005-05-26 17:18 ` Bruce Ellis
2005-05-26 18:23 ` Charles Forsyth
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 18:44 Ben Huntsman
2005-05-26 18:55 ` jmk
2005-05-26 16:52 Brantley Coile
2005-05-26 17:02 ` Bruce Ellis
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=ee9e417a0505261016798fd0bd@mail.gmail.com \
--to=russcox@gmail.com \
--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).