From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: alef bug
Date: Thu, 16 Nov 1995 15:27:11 -0500 [thread overview]
Message-ID: <19951116202711.BjtbwWObIEIJNMNwmkvMg0b-WKi860Hz8MnTGND3Pw8@z> (raw)
a student found an unpleasant feature of !{} which turns out to be a bug
on closer examination. for example:
#include <alef.h>
void
crit2 (void)
!{
print ("world\n");
}
void
crit1 (void)
!{
print ("hello\n");
crit2 ();
}
void
main (void)
{
crit1 ();
}
this locks up because internnode uses
sprint(buf, ".i%d", stmp++);
but stmp is reset by fundecl (possibly right for some calls of internnode,
but not in this case). the result is that several !{} in different functions
end up using the same synchronisation variable (but not if they appear
in the same function, or different source files).
reply other threads:[~1995-11-16 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19951116202711.BjtbwWObIEIJNMNwmkvMg0b-WKi860Hz8MnTGND3Pw8@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).