From: Joern Rennecke <amylaar@cygnus.co.uk>
To: chris@lslsun.epfl.ch (Christian Iseli)
Cc: egcs@cygnus.com
Subject: Re: Small problem in cse
Date: Tue, 28 Oct 1997 07:11:00 -0000 [thread overview]
Message-ID: <199710281511.PAA04997@phal.cygnus.co.uk> (raw)
In-Reply-To: <199710281505.QAA24058@lslsun17.epfl.ch>
> > Fix HASH.
>
> Right :-) ... However, I'm not convinced yet that HASH is the real problem.
>
> Is there any reason that reg_qty of a given reg might change from one call
> of HASH to the next?
If the register is assigned something new, or a label is passed, that is
a valid reason. Otherwise it's probably a bug.
next prev parent reply other threads:[~1997-10-28 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-28 7:06 Christian Iseli
1997-10-28 7:11 ` Joern Rennecke [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 7:10 Christian Iseli
1997-12-06 7:51 ` Jeffrey A Law
1997-10-26 23:47 Christian Iseli
1997-10-27 6:02 ` Joern Rennecke
1997-10-20 1:43 Christian Iseli
1997-10-20 9:43 ` Jeffrey A Law
1997-10-20 13:28 ` Christian Iseli
1997-10-17 13:44 Christian Iseli
1997-10-17 19:06 ` Jeffrey A Law
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=199710281511.PAA04997@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=chris@lslsun.epfl.ch \
--cc=egcs@cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).