From: Scott Schwartz schwartz@bio.cse.psu.edu
Subject: [9fans] lmbench vs 8c
Date: Sat, 11 Jul 1998 19:56:27 -0400 [thread overview]
Message-ID: <19980711235627.AjFT07qHkJcfnLSJH3HlEJ7lraRg6I-fQ696dCfWtZc@z> (raw)
Brandon Black <photon@dtmf.com> writes:
| Interesting.... but do you get the same problems with semi-valid code?
The original program was completely valid. I chopped it down just to
the point where the compiler bug manifested.
The fix (from bobf and ken) is to change, in gc.h,
char reg[D_NONE];
to
int reg[D_NONE];
And to change the initialization in txt.c to use a loop instead of memset.
next reply other threads:[~1998-07-11 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-11 23:56 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-07-11 20:45 Brandon
1998-07-11 8:29 schwartz
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=19980711235627.AjFT07qHkJcfnLSJH3HlEJ7lraRg6I-fQ696dCfWtZc@z \
--to=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).